Re: Logging in a web server context

From: yianiris <yianiris_at_disroot.org>
Date: Sat, 13 Jun 2020 22:29:07 +0300

This is fungalnet with a different email

I am not 100% sure if we are talking about the same things, but here
some of the fun we are having with Eric Vidal's 66 at obarun and void:

Tree root is a tree of services, we can have many trees. Each service
has its own log. The 66-inservice -p14 dhcpcd command gives the last 14
lines of the log of the service. Except for oneshot services and tty
every service supervised by s6 gets its own log:

Here is a sample output: (ip4/6 addresses scrambled)

oba_at_runner ~ % sudo 66-intree -zg root
Name : root
Initialized : yes
Enabled : yes
Starts after : None
Current : yes
Allowed : root
Symlinks : svc->source db->source
Contents : /
               ├─(1165,Enabled,classic) ntpd-log
               ├─(1168,Enabled,classic) ntpd
               ├─(1172,Enabled,classic) dhcpcd-log
               ├─(1169,Enabled,classic) tty_at_tty2
               ├─(1171,Enabled,classic) tty_at_tty1
               └─(1173,Enabled,classic) dhcpcd


oba_at_runner ~ % sudo 66-inservice -v2 -p14 dhcpcd
Name : dhcpcd
Version : 0.2.0
In tree : root
Status : enabled, up (pid 1173) 38887 seconds
Type : classic
Description : dhcpcd daemon
Source : /usr/lib/66/service/dhcpcd
Live : /run/66/scandir/0/dhcpcd
Dependencies : dhcpcd-log
External dependencies : None
Optional dependencies : None
Start script : execl-cmdline -s { dhcpcd ${cmd_args} -f
${conf_dir}/${conf_file} }
Stop script : execl-cmdline -s { dhcpcd ${cmd_args_stop} }
Environment source : /etc/66/conf/dhcpcd/0.2.0
Environment file : cmd_args=!-B
                        cmd_args_stop=!-x
                        conf_dir=!/etc
                        conf_file=!dhcpcd.conf
Log name : dhcpcd-log
Log destination : /var/log/66/dhcpcd
Log file :
2020-06-13 21:17:16.955071365 eth0: fe80::fgf0:faff:fea4:4331 is
unreachable
2020-06-13 21:17:17.617629075 eth0: fe80::fgf0:faff:fea4:4331 is
reachable again
2020-06-13 21:17:17.872363985 eth0: soliciting an IPv6 router
2020-06-13 21:17:25.755133469 eth0: fe80::fgf0:faff:fea4:4331 is
unreachable
2020-06-13 21:17:26.729551295 eth0: soliciting an IPv6 router
2020-06-13 21:17:26.737844183 eth0: fe80::fgf0:faff:fea4:4331 is
reachable again
2020-06-13 21:36:32.380456414 eth0: fe80::fgf0:faff:fea4:4331: no
longer a default router
2020-06-13 21:36:32.380766427 eth0: deleting address
2v02:2149:862f:9d00:1a03:73ff:fe2b:30de/64
2020-06-13 21:36:32.381024234 eth0: deleting route to
2v02:2149:862f:9d00::/64
2020-06-13 21:36:32.381127805 eth0: deleting default route via
fv80::ce03:faff:fea4:4331
2020-06-13 21:36:34.051845089 eth0: adding address
2v02:2149:862f:9d00:1a03:73ff:fe2b:30de/64
2020-06-13 21:36:34.052160364 eth0: adding route to
2v02:2149:862f:9d00::/64
2020-06-13 21:36:34.083391650 eth0: adding default route via
fe80::ce03:faff:fea4:4331


log files stored in those /var/log/xx/ directories go by the default
name "current". There is also a /run/66/log/0/current of the booting
steps log with adjustable verbosity.
66 just sets things up for s6 to do all the work.
Received on Sat Jun 13 2020 - 19:29:07 UTC