[Fli4l_dev] Verfügbarkeit von "metalog"

[Bernd Hampel]

Am 12.12.2015 um 20:08 schrieb Peter Schiefer:
> Hallo Bernd,
> 
> Am Sat, 12 Dec 2015 18:13:51 +0100 schrieb Bernd Hampel:
> 
>> Bei meinem Test mit metalog bin ich auf folgendes gestoßen.
>> Wenn der syslogd und der klogd deaktiviert sind, werden einige Meldungen
>> die in den syslog gehörten, in das Bootprotokoll geschrieben. Diese
>> Meldungen fehlen auch bei aktiviertem metalog im logfile.
>> Das Bootprotokoll ist unter folgendem Link zu finden.
>> http://we.tl/TcvAPC71Y3
> 
> nach diesem Bootlog war metalog nicht aktiv
> 
Das ist richtig. Ich habe im ersten sChritt getestet ob ohne metalog
auch keine Meldungen kommen. Das war nicht so.

> hast du in der config/metalog.txt ev vergessen das Zeich # vor
> OPT_METALOG='yes' vergessen zu entfernen?
> 
> Zu den fehlenden bzw. falschen geschribenen Meldungen - welch meinst Du da?
> 
im Bootprotokoll sind folgende Meldungen

>> Ich teste mit fli4l-4.0.0-r43346-testing
> 
> Gruß Peter
> 
im Bootprotokoll sind das folgende Meldungen ab rc498.circd bis zum Ende.

Sat Dec 12 16:59:36 2015:  [rc498.circd]  waiting for circuits to go
online ...
Sat Dec 12 16:59:37 2015:  waiting max. 35 seconds for circ1 to become
online...
Sat Dec 12 16:59:43 2015:  circ1:q[9782]:
dhcp-dhcpcd-circuit-ctrl.sh[15663]: circ1: starting dhcpcd
Sat Dec 12 16:59:45 2015: dhcp-client: DHCP event 'PREINIT'
Sat Dec 12 16:59:46 2015: dhcp-client:     sleeping 0 seconds
Sat Dec 12 16:59:46 2015: dhcp-client: DHCP event 'NOCARRIER'
Sat Dec 12 16:59:47 2015: dhcp-client: DHCP event 'CARRIER'
Sat Dec 12 16:59:47 2015: dhcp-client:     ignoring dhcp event 'CARRIER'
Sat Dec 12 16:59:55 2015: dhcp-client: DHCP event 'BOUND'
Sat Dec 12 16:59:55 2015: dhcp-client: new_broadcast_address='192.168.6.255'
Sat Dec 12 16:59:55 2015: dhcp-client: new_dhcp_lease_time='3600'
Sat Dec 12 16:59:55 2015: dhcp-client: new_dhcp_message_type='5'
Sat Dec 12 16:59:55 2015: dhcp-client: new_dhcp_rebinding_time='3150'
Sat Dec 12 16:59:55 2015: dhcp-client: new_dhcp_renewal_time='1800'
Sat Dec 12 16:59:55 2015: dhcp-client:
new_dhcp_server_identifier='192.168.6.1'
Sat Dec 12 16:59:55 2015: dhcp-client: new_domain_name='test'
Sat Dec 12 16:59:55 2015: dhcp-client: new_domain_name_servers='192.168.6.1'
Sat Dec 12 16:59:55 2015: dhcp-client: new_ip_address='192.168.6.28'
Sat Dec 12 16:59:55 2015: dhcp-client: new_network_number='192.168.6.0'
Sat Dec 12 16:59:55 2015: dhcp-client: new_routers='192.168.6.1'
Sat Dec 12 16:59:55 2015: dhcp-client: new_subnet_cidr='24'
Sat Dec 12 16:59:55 2015: dhcp-client: new_subnet_mask='255.255.255.0'
Sat Dec 12 16:59:55 2015: dhcp-client: Event: up, local:
'192.168.6.28/24', remote: '192.168.6.1'
Sat Dec 12 16:59:56 2015: prefix-up[16465]: circ1[eth1]: IPv4 prefix
192.168.6.0/24 has appeared
Sat Dec 12 16:59:59 2015: prefix-up[16465]: executing
/etc/ppp/prefix-up050.circuits-net
Sat Dec 12 17:00:02 2015: circ1 is online (which took 19 seconds)
Sat Dec 12 17:00:03 2015: [rc900.recover] add recover-option to
mini-httpd ...
Sat Dec 12 17:00:03 2015: OK
Sat Dec 12 17:00:04 2015: [rc910.arping] check state of hosts ...
Sat Dec 12 17:00:04 2015: start daemon to check online/offline state of
hosts
Sat Dec 12 17:00:04 2015: OK
Sat Dec 12 17:00:05 2015: [rc941.wol]   setting up WakeOnLan (etherwake)
Sat Dec 12 17:00:06 2015: OK
Sat Dec 12 17:00:06 2015: [rc950.easycron]  starting crond ...
Sat Dec 12 17:00:06 2015: OK
Sat Dec 12 17:00:07 2015: [rc980.acpid]    starting ACPI daemon ...
Sat Dec 12 17:00:07 2015: OK
Sat Dec 12 17:00:07 2015: Dec 12 17:00:07 acpid: starting up with
netlink and the input layer
Sat Dec 12 17:00:07 2015: Dec 12 17:00:07 acpid: 1 rule loaded
Sat Dec 12 17:00:07 2015: Dec 12 17:00:07 acpid: waiting for events:
event logging is on
Sat Dec 12 17:00:07 2015: [rc998.base] finishing boot process ...
Sat Dec 12 17:00:08 2015: OK
Sat Dec 12 17:00:11 2015: prefix-up[16465]: executing
/etc/ppp/prefix-up300.logip
Sat Dec 12 17:00:12 2015: addr-up[18596]: circ1[eth1]: IPv4 address
192.168.6.28/24 has appeared
Sat Dec 12 17:00:13 2015: addr-up[18596]: executing
/etc/ppp/addr-up300.logip
Sat Dec 12 17:00:14 2015: ip-up[18549]: executing ip-up scripts for
circ1[eth1]
Sat Dec 12 17:00:14 2015: ip-up[18549]: circuit circ1[eth1] comes up
Sat Dec 12 17:00:14 2015: ip-up[18549]: circ1: local IPv4 address:
192.168.6.28/24
Sat Dec 12 17:00:14 2015: ip-up[18549]: circ1: remote IPv4 address:
192.168.6.1
Sat Dec 12 17:00:17 2015: ip-up[18549]: executing
/etc/ppp/ip-up050.conntrack
Sat Dec 12 17:00:17 2015: ip-up[18549]: conntrack v1.4.2
(conntrack-tools): 15 flow entries have been deleted.
Sat Dec 12 17:00:17 2015: ip-up[18549]: executing /etc/ppp/ip-up200.dhcp
Sat Dec 12 17:00:17 2015: ip-up[18549]: executing /etc/ppp/ip-up200.dns
Sat Dec 12 17:00:17 2015: ip-up[18549]: using nameserver 192.168.6.1
Sat Dec 12 17:00:17 2015: ip-up[18549]: forwarding .168.192.in-addr.arpa
to 192.168.6.1
Sat Dec 12 17:00:17 2015: ip-up[18549]: killall: can't kill pid 13482:
No such process
Sat Dec 12 17:00:18 2015: ip-up[18549]: executing /etc/ppp/ip-up500.chrony
Sat Dec 12 17:00:18 2015: ip-up[18549]: restarting chronyd
Sat Dec 12 17:00:18 2015: ip-up[18549]: now restart chronyd with '-r -4'
as options
Sat Dec 12 17:00:23 2015: fli4l boot finished - VERSION:
4.0.0-r43346-testing KERNEL: 4.3.0 ARCH: i686
Sat Dec 12 17:00:23 2015: terminating bootlogd to close bootlog ...


Gruß Bernd