When I start freenet with the init-script the Webservice is unreachable. When I execute "/etc/init.d/freenet status" is this message prompt: * status: started [ ok ] Freenet 0.7 is not running. Reproducible: Always Steps to Reproduce: 1. Install freenet-ebuild 2. Start the deamon with the init-script (/etc/init.d/freenet start) 3. try http://localhost:8888 Actual Results: Website is unreachable. Expected Results: Freenet administration GUI expected. The fault is that the ebuild creates /var/freenet with wrong permissions. The root is the owner and the deamon runs as "freenet" user. The pid-File can't create by the freenet user at /var/freenet and the the deamon stops quietly. When I changed the owner of /var/freenet to the freenet user the deamon runs fine. The init-script should check the existence of the pid-file in /var/freenet/
Did the freenet user exist previously on your system? If yes, with which homedir? Did /var/freenet exist previously on your system? If yes, with which permissions?
(In reply to comment #1) > Did the freenet user exist previously on your system? If yes, with which > homedir? Yes, it exist previously. The homedir was /home/freenet. > Did /var/freenet exist previously on your system? If yes, with which > permissions? > Yes, it exist previously, too. Only user root and group root have rwx on it. After I realize that I've deleted /var/freenet and remerged freenet-ebuild again. /var/freenet was created but the owner was root again. Is this happend because the homedir was already defined to /home/freenet?
Please try this and report back: - emerge -C freenet -remove the freenet user -remove the freenet group -remove /var/freenet -remerge freenet I did local tests and for me the owner of the dir is the freenet user, probably because of it being the homdir while creating the user.
Sorry, my fault. This happens because relics of an older installation of freenet. When the user and the group not exists the permissions of /var/freenet were set correctly. Thanks for spending time.
Is this really fixed? The startup script fails silently when the permissions on /var/freenet are wrong... shouldn't there be a check and error message if so? I ran into the same problem today.
