log symlink overwritten, log dir empty. what now?

Discussion in 'Installation/Configuration' started by manarak, Nov 5, 2013.

  1. manarak

    manarak Member

    In any client's FTP environment, the log symlink keeps getting removed and replaced by an empty log directory.

    I found this on the subject:

    not a bug... ok.
    get help on the forums with configuration problems of my server...
    that's a bit harsh considering I was perfectly happy with the symlink before it got changed, the reason is apparently that chrooted users cannot access the logs through the symlink.
    I fail to see how removing that ability for everybody is an improvement...

    except, of course, if a better way is provided.

    So how can access to the logs from FTP be restored?

    Thank you
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Access to ftp logs works fine, just tested it with ispconfig here on a server. So what you complain here about is a configuration issue of your server and not a issue in ispconfig. The new method to bind mount the log directory instead of symlinking it works much better and even for chrooted users then the old version btw.

    Check if the log files are written correctly in /var/log/ispconfig/httpd/domain.tld and that the bind mounts for the logfile directorys whch point to the actual directory /var/log/ispconfig/httpd/domain.tld in /etc/fstab exist.
  3. manarak

    manarak Member

    I upgraded to recently and all I can see is an empty dir.

    The logs are written correctly in /var/log/ispconfig/httpd/domain.tld , that where I used to point the symlink to.

    isn't the upgrade process setting the correct bind mounts?
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    The symlinks are removed and replaced by a fstab entry when a website gets udated the next time e.g. when you edit and save it.Untl then, the symlinks will stay in place. This is done transparently and automatically, so you normally wont recognize this change except that the logs start to be accessible by chrooted ssh users.

    Take a look at /etc/fstab, you should see a line in there like this:

    /var/log/ispconfig/httpd/test.int /var/www/clients/client0/web1/log    none    bind,nobootwait    0 0
    for each log directory after it was converted. Dont expect to see all dirs there already as the conversion takes place when a site gets edited, not when you update ispconfig.
  5. manarak

    manarak Member

    Yes, I see this line:

    /var/log/ispconfig/httpd/domain.com /var/www/clients/client1/web1/log    none    bind,nobootwait    0 0
    but ...web1/log is empty under FTP.

    does something need to be restarted after the upgrade?
  6. till

    till Super Moderator Staff Member ISPConfig Developer


    Try to run:

    mount -a

    and check again if you see the log files.
  7. manarak

    manarak Member

    permission denied of course, I'm on a virtual server.

    maybe an option in ISPC is needed: mount or symlink
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    You can do bind mounts on virtual servers as well. All my srvers are virtualized and I install ispconfig on client systems daily were many of them are virtualized as well, the bind mount worked on all of them. You should contact your host about this isue, mos likely they block something on your server.
  9. manarak

    manarak Member


    no mounting allowed.
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Did not know that someone is still using it, no news since 2009. For a slim linux kernel based virtualisation, you might want to check out OpenVZ. I use it for several yaers on my servers, works great.
  11. manarak

    manarak Member

    unfortunately, I must use what my host offers.
    They also have KVM, but only in bigger packages and it costs double!

    Or is it easy to completely separate operations between 2 IPs on the same Vserver, with different hostname and all?
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    there can only be one hostname in a operating system instance. so if you add 2 IP addresses to the same instance, they will share the same IP adress.
  13. manarak

    manarak Member

    That's what I thought.
    Or, the way would be to run virtualization software on the KVM vServer, LOL.

Share This Page