Public bug reported:
Immediately after installing the package, I was able to launch Bricolage
at localhost:8080. But after a reboot, the browser told me there was no
server at that address. Manually running bric_apachectl start didn't
help.
My /var/log/bricolage/error.log read:
[Fri Sep 8 03:17:24 2006] [info] created shared memory segment #4325399
[Fri Sep 8 03:17:25 2006] [notice] Apache/1.3.34 (Ubuntu) mod_perl/1.29
configured -- resuming normal operations
[Fri Sep 8 03:17:25 2006] [info] Server built: Jan 7 2006 16:00:45
[Fri Sep 8 03:17:25 2006] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Fri Sep 8 03:35:07 2006] [error] access to /login failed for 127.0.0.1,
reason: Invalid username or password. Please try again.
[Fri Sep 8 03:36:50 2006] [error] access to /login failed for 127.0.0.1,
reason: Invalid username or password. Please try again.
[Fri Sep 8 03:45:53 2006] [warn] child process 32745 still did not exit,
sending a SIGTERM
[Fri Sep 8 03:45:53 2006] [warn] child process 32746 still did not exit,
sending a SIGTERM
[Fri Sep 8 03:45:53 2006] [warn] child process 482 still did not exit, sending
a SIGTERM
[Fri Sep 8 03:45:53 2006] [warn] child process 483 still did not exit, sending
a SIGTERM
[Fri Sep 8 03:45:53 2006] [warn] child process 484 still did not exit, sending
a SIGTERM
[Fri Sep 8 03:45:57 2006] [error] child process 32745 still did not exit,
sending a SIGKILL
[Fri Sep 8 03:45:57 2006] [error] child process 32746 still did not exit,
sending a SIGKILL
[Fri Sep 8 03:45:57 2006] [error] child process 482 still did not exit,
sending a SIGKILL
[Fri Sep 8 03:45:57 2006] [error] child process 483 still did not exit,
sending a SIGKILL
[Fri Sep 8 03:45:57 2006] [error] child process 484 still did not exit,
sending a SIGKILL
[Fri Sep 8 03:45:57 2006] [info] removed PID file
/var/run/bricolage/bricolage.pid (pid=32744)
[Fri Sep 8 03:45:57 2006] [notice] caught SIGTERM, shutting down
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
fopen: No such file or directory
apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid
Further investigation revealed there was no bricolage directory in
/var/run, which is owned by root. Others can read and execute there, but
not write. Bricolage is set in the config file to run as user bricolage.
I was able to get bricolage running again by manually creating
/var/run/bricolage with sudo and making user bricolage the owner.
I wish I'd been more patient during installation of the package, because
I seem to recall some kind of errors or warnings involving permissions
problems. I'd be happy to post any other logs I have that may help if
you can tell me where to look for them.
** Affects: bricolage (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
PID file problem
https://launchpad.net/bugs/59793
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
