* bug#59181: [berlin] web services fail to start on reboot due to anonip
@ 2022-11-10 18:16 Maxim Cournoyer
2024-11-01 8:30 ` Maxim Cournoyer
0 siblings, 1 reply; 3+ messages in thread
From: Maxim Cournoyer @ 2022-11-10 18:16 UTC (permalink / raw)
To: 59181
Hi,
Each time we reboot berlin, we must clear anonip files that it uses to
process the nginx logs, which are supposed to be named pipes rather than
empty files, like so:
# rm /var/run/anonip/*
# herd start nginx
We should fix that.
--
Thanks,
Maxim
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#59181: [berlin] web services fail to start on reboot due to anonip
2022-11-10 18:16 bug#59181: [berlin] web services fail to start on reboot due to anonip Maxim Cournoyer
@ 2024-11-01 8:30 ` Maxim Cournoyer
2024-11-01 14:02 ` Maxim Cournoyer
0 siblings, 1 reply; 3+ messages in thread
From: Maxim Cournoyer @ 2024-11-01 8:30 UTC (permalink / raw)
To: 59181; +Cc: Ricardo Wurmus
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi,
>
> Each time we reboot berlin, we must clear anonip files that it uses to
> process the nginx logs, which are supposed to be named pipes rather than
> empty files, like so:
>
> # rm /var/run/anonip/*
> # herd start nginx
>
> We should fix that.
OK, I've now narrowed this issue down to the nginx activation script,
which validates the configuration file, which causes nginx to write the
log files before our anonip service gets to create the named pipes at
their location.
Here's a small debug session in a VM showing this is the case:
--8<---------------cut here---------------start------------->8---
root@komputilo ~# ls /var/run/anonip
access.log error.log
root@komputilo ~# rm /var/run/anonip/*
root@komputilo ~# ls /var/run/anonip
root@komputilo ~# "/gnu/store/kn56akgnfkqm0ppyfzhyh63ss06ff42s-nginx-1.27.1/sbin/nginx" "-c" "/gnu/store/zc2vj9ixcmdpkivkdyp16vw8lyaivvky-nginx.conf" "-p" "/var/run/nginx" "-t"
nginx: the configuration file /gnu/store/zc2vj9ixcmdpkivkdyp16vw8lyaivvky-nginx.conf syntax is ok
root@komputilo ~# ls /var/run/anonip
access.log error.log
--8<---------------cut here---------------end--------------->8---
I suggest we simply recreate the log files in our anonip service start
slot; currently it checks and fails if they already exist.
--
Thanks,
Maxim
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#59181: [berlin] web services fail to start on reboot due to anonip
2024-11-01 8:30 ` Maxim Cournoyer
@ 2024-11-01 14:02 ` Maxim Cournoyer
0 siblings, 0 replies; 3+ messages in thread
From: Maxim Cournoyer @ 2024-11-01 14:02 UTC (permalink / raw)
To: 59181-done, guix-sysadmin; +Cc: Ricardo Wurmus
Hi,
I've pushed a fix for this as commit 49375f83fc. The tests I've
implemented to help troubleshoot the issue are up for review in
https://issues.guix.gnu.org/74151.
I haven't yet reconfigured berlin with it but will do so next night,
European time.
A fully functional reboot at last awaits :-)
--
Thanks,
Maxim
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-11-01 14:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-10 18:16 bug#59181: [berlin] web services fail to start on reboot due to anonip Maxim Cournoyer
2024-11-01 8:30 ` Maxim Cournoyer
2024-11-01 14:02 ` Maxim Cournoyer
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.