[fli4l] Opt_OAC Block @ BOOT hat keine Wirkung

Klaus Backhaus backhaus at tu-harburg.de
Fr Mai 5 16:32:28 CEST 2017


Hallo Heinz-Peter:
> Hallo Klaus,
>
>> Wo liegt meine Fehler?
>
> gibt es irgendwelche Hinweise im bootlog?
Im bootlog ist alles "grün"
also nichts auffälliges

> Ist das syslog aktiviert? Ansonsten bitte einschalten und mal schauen.
>
Noch nicht
Werde ich gleich MONTAG morgen machen

Für diese Woche die Nase voll

Wünsche ein SONNIGES WE!!!

Vielen Dank für Deine Mühe!

Hänge sie doch noch unten dran (macht das entsorgen einfacher)
> Gruß
> Heinz-Peter
>
Gruß
Klaus

  rootfs on / type rootfs (rw,size=254932k,nr_inodes=63733)
  proc on /proc type proc (rw,relatime)
  sysfs on /sys type sysfs (rw,relatime)
  devpts on /dev/pts type devpts (rw,relatime,mode=600)
  ^[[32m^[[49m   running boot scripts^[[0m
  ^[[32m^[[49m-> basic setup for booting... (/etc/boot.d/rc000.base)^[[0m
  ^[[32m^[[49m   Wrapping of modutils disabled ()^[[0m
  ^[[32m^[[49m-> finished basic setup for booting... 
(/etc/boot.d/rc000.base)^[[0m
  ^[[32m^[[49m-> loading USB core drivers ... (/etc/boot.d/rc005.usb)^[[0m
  ^[[32m^[[49m-> finished loading USB core drivers ... 
(/etc/boot.d/rc005.usb)^[[0m
  ^[[32m^[[49m-> loading generic disk drivers ... 
(/etc/boot.d/rc020.hd-generic)^[[0m
  ^[[32m^[[49m-> finished loading generic disk drivers ... 
(/etc/boot.d/rc020.hd-generic)^[[0m
  ^[[32m^[[49m-> loading USB storage drivers ... 
(/etc/boot.d/rc030.usb)^[[0m
  ^[[32m^[[49m-> finished loading USB storage drivers ... 
(/etc/boot.d/rc030.usb)^[[0m
  ^[[32m^[[49m-> waiting for USB bus initial emumeration ... 
(/etc/boot.d/rc030.usb)^[[0m
  ^[[32m^[[49m   Waiting for USB bus to settle up.^[[0m
  ^[[32m^[[49m-> finished waiting for USB bus initial emumeration ... 
(/etc/boot.d/rc030.usb)^[[0m
  ^[[32m^[[49m-> scanning for partition tables on storage ... 
(/etc/boot.d/rc040.partitions)^[[0m
   sda: sda1
  ^[[32m^[[49m-> finished scanning for partition tables on storage ... 
(/etc/boot.d/rc040.partitions)^[[0m
  ^[[32m^[[49m-> mounting boot device ... (/etc/boot.d/rc100.hdboot)^[[0m
  fsck.fat 3.0.26 (2014-03-07)
  There are differences between boot sector and its backup.
  This is mostly harmless. Differences: (offset:original/backup)

   ===== snip
    Not automatically fixing this.
  /
    Bad short file name ().
    Auto-renaming it.
    Renamed to
  /dev/sda1: 14 files, 178/976575 clusters
  ^[[32m^[[49m-> finished mounting boot device ... 
(/etc/boot.d/rc100.hdboot)^[[0m
  ^[[32m^[[49m-> unpacking opt archive ... (/etc/boot.d/rc100.hdboot)^[[0m
  ^[[32m^[[49m   extracting files from opt archive^[[0m
  ......
  ^[[32m^[[49m-> finished unpacking opt archive ... 
(/etc/boot.d/rc100.hdboot)^[[0m
  ^[[32m^[[49m   finished boot scripts^[[0m
  boot_dev=/dev/sda1
  boot_fs=vfat
  hd_data=
  ^[[32m^[[49m-> checking for known problems ... (/etc/rc.d/rc000._bug)^[[0m
  ^[[32m^[[49m-> finished checking for known problems ... 
(/etc/rc.d/rc000._bug)^[[0m
  ^[[32m^[[49m-> basic setup... (/etc/rc.d/rc000.base)^[[0m
  ^[[32m^[[49m-> finished basic setup... (/etc/rc.d/rc000.base)^[[0m
  ^[[32m^[[49m-> creating /etc/resolv.conf and /etc/hosts ... 
(/etc/rc.d/rc001.base)^[[0m
  ^[[32m^[[49m   writing /etc/resolv.conf ...^[[0m
  ^[[32m^[[49m   writing /etc/hosts ...^[[0m
  ^[[32m^[[49m-> finished creating /etc/resolv.conf and /etc/hosts ... 
(/etc/rc.d/rc001.base)^[[0m
  ^[[32m^[[49m-> creating hosts-files .... (/etc/rc.d/rc001.hosts)^[[0m
  ^[[32m^[[49m   writing HOSTS to /etc/hosts ...^[[0m
  ^[[32m^[[49m-> finished creating hosts-files .... 
(/etc/rc.d/rc001.hosts)^[[0m
  ^[[32m^[[49m-> preparing httpd menu and lang-support ... 
(/etc/rc.d/rc005.httpd)^[[0m
  ^[[32m^[[49m-> finished preparing httpd menu and lang-support ... 
(/etc/rc.d/rc005.httpd)^[[0m
  ^[[32m^[[49m-> loading USB drivers ... (/etc/rc.d/rc005.usb)^[[0m
  ^[[32m^[[49m   now waiting for the drivers to come up^[[0m
  ^[[32m^[[49m-> finished loading USB drivers ... (/etc/rc.d/rc005.usb)^[[0m
  ^[[32m^[[49m-> starting haveged ... (/etc/rc.d/rc090.haveged)^[[0m
  May  5 10:45:31 haveged: haveged starting up
  ^[[32m^[[49m-> finished starting haveged ... 
(/etc/rc.d/rc090.haveged)^[[0m
  ^[[32m^[[49m-> setup of persistent storage... 
(/etc/rc.d/rc099.persistent)^[[0m
  ^[[32m^[[49m   using /boot/persistent on /dev/sda1 for persistent 
storage^[[0m
  ^[[32m^[[49m-> finished setup of persistent storage... 
(/etc/rc.d/rc099.persistent)^[[0m
  ^[[32m^[[49m-> creating crontab ... (/etc/rc.d/rc100.easycron)^[[0m
  ^[[32m^[[49m-> finished creating crontab ... 
(/etc/rc.d/rc100.easycron)^[[0m
  ^[[32m^[[49m-> initializing power management subsystem ... 
(/etc/rc.d/rc100.pm)^[[0m
  ^[[32m^[[49m-> finished initializing power management subsystem ... 
(/etc/rc.d/rc100.pm)^[[0m
  ^[[32m^[[49m-> setup system time... (/etc/rc.d/rc100.time)^[[0m
  ^[[32m^[[49m-> finished setup system time... (/etc/rc.d/rc100.time)^[[0m
  ^[[32m^[[49m-> loading network drivers ... (/etc/rc.d/rc120.net)^[[0m
  ^[[32m^[[49m-> finished loading network drivers ... 
(/etc/rc.d/rc120.net)^[[0m
  ^[[32m^[[49m-> creating bonding devices... (/etc/rc.d/rc200.bonding)^[[0m
  sh: write error: Connection timed out
  ^[[32m^[[49m-> finished creating bonding devices... 
(/etc/rc.d/rc200.bonding)^[[0m
  ^[[32m^[[49m-> configuring loopback and ethernet device ... 
(/etc/rc.d/rc300.lo)^[[0m
  ^[[32m^[[49m-> finished configuring loopback and ethernet device ... 
(/etc/rc.d/rc300.lo)^[[0m
  ^[[32m^[[49m-> configuring ip on network cards ... 
(/etc/rc.d/rc305.ip-eth)^[[0m
  ^[[32m^[[49m     disabling GRO for bond0^[[0m
  ^[[32m^[[49m     disabling GRO for bond1^[[0m
  ^[[32m^[[49m-> finished configuring ip on network cards ... 
(/etc/rc.d/rc305.ip-eth)^[[0m
  ^[[32m^[[49m-> setting up additional routes ... 
(/etc/rc.d/rc320.route)^[[0m
  ^[[32m^[[49m-> finished setting up additional routes ... 
(/etc/rc.d/rc320.route)^[[0m
  ^[[32m^[[49m-> setting up default gateway ... (/etc/rc.d/rc320.route)^[[0m
  ^[[32m^[[49m-> finished setting up default gateway ... 
(/etc/rc.d/rc320.route)^[[0m
  ^[[32m^[[49m-> preparing circuits ... (/etc/rc.d/rc340.circuits)^[[0m
  ^[[32m^[[49m   writing /etc/ppp/pap-secrets ...^[[0m
  ^[[32m^[[49m-> finished preparing circuits ... 
(/etc/rc.d/rc340.circuits)^[[0m
  ^[[32m^[[49m-> configuring firewall ... (/etc/rc.d/rc360.fwrules)^[[0m
  ^[[32m^[[49m-> finished configuring firewall ... 
(/etc/rc.d/rc360.fwrules)^[[0m
  ^[[32m^[[49m-> Starting webserver ... (/etc/rc.d/rc430.httpd)^[[0m
  ^[[32m^[[49m-> finished Starting webserver ... 
(/etc/rc.d/rc430.httpd)^[[0m
  socket: Address family not supported by protocol
  ^[[32m^[[49m-> starting sshd daemon... (/etc/rc.d/rc460.dropbear)^[[0m
  ^[[32m^[[49m-> finished starting sshd daemon... 
(/etc/rc.d/rc460.dropbear)^[[0m
  ^[[32m^[[49m-> Starting Online Access Control ... 
(/etc/rc.d/rc800.oac)^[[0m
  ^[[32m^[[49m-> finished Starting Online Access Control ... 
(/etc/rc.d/rc800.oac)^[[0m
  ^[[32m^[[49m-> preparing vnstat databases ... 
(/etc/rc.d/rc900.vnstat)^[[0m
  ^[[32m^[[49mcreating new vnstat-DB for device lo^[[0m
  Error: Unable to read database "/var/lib/vnstat/lo": No such file or 
directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device eth0^[[0m
  Error: Unable to read database "/var/lib/vnstat/eth0": No such file or 
directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device eth1^[[0m
  Error: Unable to read database "/var/lib/vnstat/eth1": No such file or 
directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device eth2^[[0m
  Error: Unable to read database "/var/lib/vnstat/eth2": No such file or 
directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device eth3^[[0m
  Error: Unable to read database "/var/lib/vnstat/eth3": No such file or 
directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device eth4^[[0m
  Error: Unable to read database "/var/lib/vnstat/eth4": No such file or 
directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device eth5^[[0m
  Error: Unable to read database "/var/lib/vnstat/eth5": No such file or 
directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device bond0^[[0m
  Error: Unable to read database "/var/lib/vnstat/bond0": No such file 
or directory
  Info: -> A new database has been created.
  ^[[32m^[[49mcreating new vnstat-DB for device bond1^[[0m
  Error: Unable to read database "/var/lib/vnstat/bond1": No such file 
or directory
  Info: -> A new database has been created.
  ^[[32m^[[49m-> finished preparing vnstat databases ... 
(/etc/rc.d/rc900.vnstat)^[[0m
  ^[[32m^[[49m-> check state of hosts ... (/etc/rc.d/rc910.arping)^[[0m
  ^[[32m^[[49m   start daemon to check online/offline state of hosts^[[0m
  ^[[32m^[[49m-> finished check state of hosts ... 
(/etc/rc.d/rc910.arping)^[[0m
  ^[[32m^[[49m-> starting atd ... (/etc/rc.d/rc950.atd)^[[0m
  ^[[32m^[[49m-> finished starting atd ... (/etc/rc.d/rc950.atd)^[[0m
  ^[[32m^[[49m-> starting crond ... (/etc/rc.d/rc950.easycron)^[[0m
  ^[[32m^[[49m-> finished starting crond ... (/etc/rc.d/rc950.easycron)^[[0m
  ^[[32m^[[49m-> starting ACPI daemon ... (/etc/rc.d/rc980.acpid)^[[0m
  ^[[32m^[[49m-> finished starting ACPI daemon ... 
(/etc/rc.d/rc980.acpid)^[[0m
  acpid: starting up with netlink and the input layer
  acpid: 1 rule loaded
  acpid: waiting for events: event logging is on
  ^[[32m^[[49m-> registering ip-up and ip-down event hooks 
(/etc/rc.d/rc990.base)^[[0m
  ^[[32m^[[49m-> finished registering ip-up and ip-down event hooks 
(/etc/rc.d/rc990.base)^[[0m
  ^[[32m^[[49m-> finishing boot process ... (/etc/rc.d/rc998.base)^[[0m
  ^[[32m^[[49m   Emitting ip-up event for dev=bond1 local=aaa.bbb.ccc.7 
remote=aaa.bbb.ccc.7...^[[0m
  ip-up[2717]: starting (bond1 /dev/null 0 aaa.bbb.ccc.7 aaa.bbb.ccc.7)...
  ip-up[2717]: executing ip-up scripts ...
  ip-up[2717]: default route interface 'bond1' comes up
  ip-up[2717]: executing /etc/ppp/ip-up020.fwsetup
  ip-up[2717]: setting up dynamic IPv4 firewall rules ...
  ip-up[2717]: executing /etc/ppp/ip-up050.conntrack
  ip-up[2717]: conntrack v1.4.2 (conntrack-tools): 0 flow entries have 
been deleted.
  ip-up[2717]: executing /etc/ppp/ip-up900.user
  ip-up[2717]:
  ip-up[2717]: executing /etc/ppp-once/ip-up001.ppp-onceflag
  ip-up[2717]: finished ip-up scripts ...
  ip-up[2717]: terminating ...
  ^[[32m^[[49m   ...done^[[0m
  ^[[32m^[[49m-> finished finishing boot process ... 
(/etc/rc.d/rc998.base)^[[0m
  ^[[32m^[[49m   fli4l boot finished - VERSION: 3.10.9 KERNEL: 3.14.79 
ARCH: i686 ^[[0m
  ^[[32m^[[49m   terminating bootlogd to close bootlog ...^[[0m



Mehr Informationen über die Mailingliste Fli4L