suspected timezone mismatch in /etc mouting on boot

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
att
Contributor
Contributor
Posts: 131
Joined: 28 Dec 2010, 17:09

suspected timezone mismatch in /etc mouting on boot

Post#1 by att » 03 Aug 2016, 18:53

Hi,

I have a weird problem with my Porteus USB stick. I notice that in /var/log/messages, the time is wrong, especially at booting.
For example:

Code: Select all

root@rechner:/var/log# less messages

Aug  1 09:37:13 rechner syslogd 1.5.0: restart.
Aug  1 09:37:14 rechner kernel: klogd 1.5.0, log source = /proc/kmsg started.
Aug  1 09:37:14 rechner kernel: [    0.000000] Initializing cgroup subsys cpu
Aug  1 09:37:14 rechner kernel: [    0.000000] Linux version 3.13.6-rechner (root@rechner) (gcc version 4.8.2 (GCC) ) #1 SMP PREEMPT Fri Mar 7 06:53:36 Local time zone must be set--s
Aug  1 09:37:14 rechner kernel: [    0.000000] Command line: initrd=initrd.xz 3 copy2ram nonetwork timezone=Europe/Vienna volume=1% kmap=at BOOT_IMAGE=vmlinuz
Aug  1 09:37:14 rechner kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Aug  1 09:37:14 rechner kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009a7ff] usable

[*snip to the interesting part:*]

Aug  1 09:37:14 rechner kernel: [    2.492525] Switched to clocksource tsc
Aug  1 09:37:14 rechner kernel: [    2.961417] random: nonblocking pool is initialized
Aug  1 09:37:14 rechner kernel: <30>[    5.919340] udevd[2345]: starting version 182
Aug  1 09:37:14 rechner kernel: [    6.954551] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Aug  1 09:37:14 rechner kernel: [    6.980230] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Aug  1 09:37:14 rechner kernel: [    7.004260] 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Aug  1 09:37:14 rechner kernel: [    7.104954] dca service started, version 1.12.1
Aug  1 09:37:14 rechner kernel: [    7.120001] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Aug  1 09:37:14 rechner kernel: [    7.123835] pps_core: LinuxPPS API ver. 1 registered
Aug  1 09:37:14 rechner kernel: [    7.123844] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Aug  1 09:37:15 rechner kernel: [    7.128624] PTP clock support registered
Aug  1 09:37:15 rechner kernel: [    7.186500] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k
Aug  1 09:37:15 rechner kernel: [    7.186511] igb: Copyright (c) 2007-2013 Intel Corporation.
Aug  1 09:37:15 rechner kernel: [    7.289529] 0000:00:14.0: ttyS2 at I/O 0xf000 (irq = 16, base_baud = 115200) is a 16550A
Aug  1 09:37:15 rechner kernel: [    7.333860] igb 0000:05:00.0: added PHC on eth0
Aug  1 09:37:15 rechner kernel: [    7.333871] igb 0000:05:00.0: Intel(R) Gigabit Ethernet Network Connection
Aug  1 09:37:15 rechner kernel: [    7.333880] igb 0000:05:00.0: eth0: (PCIe:5.0Gb/s:Width x2) 00:25:90:e4:63:86
Aug  1 09:37:15 rechner kernel: [    7.333967] igb 0000:05:00.0: eth0: PBA No: 106100-000
Aug  1 09:37:15 rechner kernel: [    7.333974] igb 0000:05:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Aug  1 09:37:15 rechner kernel: [    7.496540] igb 0000:05:00.1: added PHC on eth1
Aug  1 09:37:15 rechner kernel: [    7.496550] igb 0000:05:00.1: Intel(R) Gigabit Ethernet Network Connection
Aug  1 09:37:15 rechner kernel: [    7.496559] igb 0000:05:00.1: eth1: (PCIe:5.0Gb/s:Width x2) 00:25:90:e4:63:87
Aug  1 09:37:15 rechner kernel: [    7.496645] igb 0000:05:00.1: eth1: PBA No: 106100-000
Aug  1 09:37:15 rechner kernel: [    7.496653] igb 0000:05:00.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Aug  1 09:37:15 rechner mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:02.0/0000:02:00.0/usb1/1-4"
Aug  1 09:37:15 rechner mtp-probe: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:02.0/0000:02:00.0/usb1/1-1"
Aug  1 09:37:15 rechner mtp-probe: bus: 1, device: 3 was not an MTP device
Aug  1 09:37:15 rechner mtp-probe: bus: 1, device: 2 was not an MTP device
Aug  1 11:37:19 rechner init: Entering runlevel: 3 ;;         -----> now the clock is correct!
Aug  1 11:37:19 rechner acpid: starting up with netlink and the input layer
Aug  1 11:37:19 rechner acpid: 4 rules loaded
Aug  1 11:37:19 rechner acpid: waiting for events: event logging is off
Aug  1 09:37:19 rechner dhcpcd[2976]: version 6.0.5 starting  ;;     ------> now the clock is wrong again!
Aug  1 09:37:19 rechner dhcpcd[2976]: eth0: waiting for carrier
Aug  1 09:37:23 rechner kernel: [   15.854340] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Aug  1 09:37:23 rechner dhcpcd[2976]: eth0: carrier acquired
Aug  1 09:37:23 rechner dhcpcd[2976]: eth0: soliciting a DHCP lease
Aug  1 09:37:24 rechner dhcpcd[2976]: eth0: offered 192.168.0.156 from 192.168.0.174
Aug  1 09:37:30 rechner dhcpcd[2976]: eth0: leased 192.168.0.156 for 1800 seconds
Aug  1 09:37:30 rechner dhcpcd[2976]: eth0: adding host route to 192.168.0.156 via 127.0.0.1
Aug  1 09:37:30 rechner dhcpcd[2976]: eth0: adding route to 192.168.0.0/24
Aug  1 09:37:30 rechner dhcpcd[2976]: eth0: adding default route via 192.168.0.174
Aug  1 09:37:30 rechner dhcpcd[2976]: forked to background, child pid 3023

--------- 

You can see that at entering Runlevel 3, suddenly the time is correct, but only for 4 lines in the log. As soon as DHCP starts, the clock is wrong again.
I asked some linux expert and he said:
I looked shortly at [core.xzm]/etc/rc.d/rc.S of porteus -- syslog is started, before localtime is copied to /etc.
If I am not mistaken, at that moment klogd is running in the wrong timezone and syslogd in the right timezone.
I guess this happens up to the syslog restart in runlevel 3.
Can you confirm this? Has anyone else this problem? How to fix it? The used porteus distro is 3.0 / 64bit.

Any help appreciated!

User avatar
francois
Contributor
Contributor
Posts: 5068
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: suspected timezone mismatch in /etc mouting on boot

Post#2 by francois » 04 Aug 2016, 16:11

Hello att,

We are about to release porteus 3.2. :wink:
Voltaire: Le mieux est l'ennemi du bien.

User avatar
Ed_P
Contributor
Contributor
Posts: 3314
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: suspected timezone mismatch in /etc mouting on boot

Post#3 by Ed_P » 04 Aug 2016, 20:50

francois wrote:We are about to release porteus 3.2.
"about to" :shock: You know something we don't? :unknown:
Ed

User avatar
francois
Contributor
Contributor
Posts: 5068
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: suspected timezone mismatch in /etc mouting on boot

Post#4 by francois » 04 Aug 2016, 23:45

Frankly, aren't too the guy I met on porteus 3.2 rc4? 8)
Voltaire: Le mieux est l'ennemi du bien.

User avatar
Ed_P
Contributor
Contributor
Posts: 3314
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: suspected timezone mismatch in /etc mouting on boot

Post#5 by Ed_P » 05 Aug 2016, 02:24

And on porteus 3.2 rc1, porteus 3.2 rc2 and porteus 3.2 rc3. And hopefully on porteus 3.2 rc5 and porteus 3.2 rc6 and finally on porteus 3.2. I'm expecting November but if December works that's fine. No hurry.
Ed

User avatar
francois
Contributor
Contributor
Posts: 5068
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: suspected timezone mismatch in /etc mouting on boot

Post#6 by francois » 09 Aug 2016, 23:09

From what I know, I could say you are wrong. :wink:

But this is off topic. :)
Voltaire: Le mieux est l'ennemi du bien.

att
Contributor
Contributor
Posts: 131
Joined: 28 Dec 2010, 17:09

Re: suspected timezone mismatch in /etc mouting on boot

Post#7 by att » 11 Aug 2016, 16:16

You guys are very off topic.
Now, is this a confirmed bug in Porteus 3.0/64bit or not?
Has anyone noticed this timezone bug or not ?
And how to fix this bug?

User avatar
Ed_P
Contributor
Contributor
Posts: 3314
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: suspected timezone mismatch in /etc mouting on boot

Post#8 by Ed_P » 11 Aug 2016, 17:31

I run Portues 3.0.1 64-bit but I am unable to reproduce your output.

Code: Select all

guest@porteus:~$ less messages
messages: No such file or directory
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# less messages
messages: No such file or directoryhis is my log
root@porteus:/home/guest# 
This is some of my cat /var/log/syslog. Times do seem out of sync at times.

Code: Select all

Aug 10 17:10:01 porteus NetworkManager[2367]: <warn> (pid 9858) unhandled DHCP event for interface eth1
Aug 10 17:10:01 porteus last message repeated 2 times
Aug 10 19:47:24 porteus kernel: [ 4347.753355] Freezing user space processes ... (elapsed 0.002 seconds) done.
Aug 10 19:47:24 porteus kernel: [ 4347.755946] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Aug 10 19:47:24 porteus kernel: [ 4347.757682] Suspending console(s) (use no_console_suspend to debug)
Aug 10 19:47:24 porteus kernel: [ 4348.636931] Disabling non-boot CPUs ...
Aug 10 19:47:24 porteus kernel: [ 4350.368926] Restarting tasks ... done.
Aug 10 19:47:27 porteus NetworkManager[2367]: <warn> Trying to remove a non-existant call id.
Aug 10 19:51:04 porteus avahi-daemon[2331]: Disconnected from D-Bus, exiting.
Aug 10 19:51:04 porteus avahi-dnsconfd[2394]: read(): EOF
Aug 10 19:51:04 porteus NetworkManager[2367]: <warn> disconnected by the system bus.
Aug 10 19:51:04 porteus ModemManager[2443]: <warn>  Could not acquire the 'org.freedesktop.ModemManager1' service name 
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: RSDP 00000000000fe020 000024 (v02 ACRSYS)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: XSDT 000000006eef5120 000064 (v01 ACRSYS ACRPRDCT 00000003      01000013)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: FACP 000000006eef4000 0000F4 (v04 ACRSYS ACRPRDCT 00000003 1025 00040000)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: DSDT 000000006eee8000 0089F9 (v01 ACRSYS ACRPRDCT F0000000 1025 00040000)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: FACS 000000006ee97000 000040
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: HPET 000000006eef3000 000038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: APIC 000000006eef2000 000084 (v02 ACRSYS ACRPRDCT 00000001 1025 00040000)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: MCFG 000000006eef1000 00003C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: BOOT 000000006eee7000 000028 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: SLIC 000000006eee6000 000176 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: SSDT 000000006eee5000 00030C (v01 AMD    POWERNOW 00000001 AMD  00000001)
Aug 10 15:52:56 porteus kernel: [    0.000000] ACPI: SSDT 000000006eee3000 00168E (v02    AMD     ALIB 00000001 MSFT 04000000)
Aug 10 15:52:56 porteus kernel: [    0.000000] Zone ranges:
Aug 10 15:52:56 porteus kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Aug 10 15:52:56 porteus kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Aug 10 15:52:56 porteus kernel: [    0.000000]   Normal   empty
Aug 10 15:52:56 porteus kernel: [    0.000000] Movable zone start for each node
Aug 10 15:52:56 porteus kernel: [    0.000000] Early memory node ranges
Aug 10 15:52:56 porteus kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009bfff]
Aug 10 15:52:56 porteus kernel: [    0.000000]   node   0: [mem 0x00100000-0x6d639fff]
Aug 10 15:52:56 porteus kernel: [    0.000000]   node   0: [mem 0x6d83a000-0x6ed3efff]
Aug 10 15:52:56 porteus kernel: [    0.000000]   node   0: [mem 0x6eef6000-0x6eefffff]
Aug 10 15:52:56 porteus kernel: [    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 446227
Aug 10 15:52:56 porteus kernel: [    0.000000] Policy zone: DMA32
Aug 10 15:52:56 porteus kernel: [    0.000000] Memory: 1775508K/1813392K available (4638K kernel code, 561K rwdata, 1188K rodata, 832K init, 624K bss, 37884K reserved)
Aug 10 15:52:56 porteus kernel: [    0.011477] ACPI: All ACPI Tables successfully acquired
Aug 10 15:52:56 porteus kernel: [    0.202681] ACPI: Executed 1 blocks of module-level executable AML code
Aug 10 15:52:56 porteus kernel: [    0.231323] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580)
Aug 10 15:52:56 porteus kernel: [    0.231337] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
Aug 10 15:52:56 porteus udevd[1716]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/80-brother-libsane-type1.rules:17 
Aug 10 15:52:56 porteus udevd[1716]: invalid rule '/etc/udev/rules.d/80-brother-libsane-type1.rules:17' 
Aug 10 15:52:56 porteus kernel: [    0.548235] ACPI: Enabled 2 GPEs in block 00 to 1F
Aug 10 15:52:56 porteus kernel: [    5.768404] REISERFS warning (device loop5): sh-2006 read_super_block: bread failed (dev loop5, block 2, size 4096)
Aug 10 15:52:56 porteus kernel: [    5.768422] REISERFS warning (device loop5): sh-2006 read_super_block: bread failed (dev loop5, block 16, size 4096)
Aug 10 15:52:56 porteus kernel: [    5.800920] REISERFS warning (device loop6): sh-2006 read_super_block: bread failed (dev loop6, block 16, size 4096)
Aug 10 15:52:56 porteus kernel: [    5.823674] REISERFS warning (device loop7): sh-2006 read_super_block: bread failed (dev loop7, block 16, size 4096)
Aug 10 15:52:56 porteus kernel: [    6.125610] REISERFS warning (device loop16): sh-2006 read_super_block: bread failed (dev loop16, block 16, size 4096)
Aug 10 15:52:56 porteus kernel: [    6.432858] REISERFS warning (device loop24): sh-2006 read_super_block: bread failed (dev loop24, block 16, size 4096)
Aug 10 15:53:00 porteus kernel: [   15.807260] wl: module license 'unspecified' taints kernel.
Aug 10 15:53:00 porteus kernel: [   15.807275] Disabling lock debugging due to kernel taint
Aug 10 15:53:01 porteus kernel: [   16.338222] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.30.223.248 (r487574)
Aug 10 19:53:06 porteus NetworkManager[2478]: <warn> failed to allocate link cache: (-12) Object not found
Aug 10 19:53:06 porteus NetworkManager[2478]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Aug 10 19:53:06 porteus NetworkManager[2478]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Aug 10 19:53:06 porteus NetworkManager[2478]: <warn> Couldn't get managed objects: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Aug 10 19:53:07 porteus NetworkManager[2478]: <warn> Trying to remove a non-existant call id.
Aug 10 19:53:10 porteus ModemManager[2505]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:15.2/0000:06:00.0': not supported by any plugin 
Aug 10 19:53:10 porteus ModemManager[2505]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:15.3/0000:07:00.0': not supported by any plugin 
Aug 10 19:58:03 porteus kernel: [  318.908029] aufs may_rename_srcdir:469:URL Classifier[3741]: renaming dir who has child(ren) on multiple branches, is not supported
Aug 10 20:27:54 porteus avahi-daemon[2389]: Disconnected from D-Bus, exiting.
Aug 10 20:27:54 porteus avahi-dnsconfd[2438]: read(): EOF
Aug 10 20:27:54 porteus NetworkManager[2478]: <warn> disconnected by the system bus.
Aug 10 20:27:54 porteus ModemManager[2505]: <warn>  Could not acquire the 'org.freedesktop.ModemManager1' service name 
Aug 11 05:00:27 porteus udevd[1716]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/80-brother-libsane-type1.rules:17 
Aug 11 05:00:27 porteus udevd[1716]: invalid rule '/etc/udev/rules.d/80-brother-libsane-type1.rules:17'
Not sure of the significance.
Ed

User avatar
francois
Contributor
Contributor
Posts: 5068
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: suspected timezone mismatch in /etc mouting on boot

Post#9 by francois » 11 Aug 2016, 21:46

What do you get in always fresh mode? Have you tried with a new save changes folder?
Voltaire: Le mieux est l'ennemi du bien.

donald
Full of knowledge
Full of knowledge
Posts: 1215
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: suspected timezone mismatch in /etc mouting on boot

Post#10 by donald » 11 Aug 2016, 23:04

@ Ed
-- slip of the pen --
OP:
root@rechner:/var/log# less messages
You:
root@porteus:/home/guest# less messages --> should be: less /var/log/messages.. :wink:

User avatar
wread
Module Guard
Module Guard
Posts: 1090
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: suspected timezone mismatch in /etc mouting on boot

Post#11 by wread » 12 Aug 2016, 00:05

@att
What is your desktop?

My desktop is Porteus KDE5-64bits and I have no issues with timezone mismatches.
What the operating system does at startup is meaningless if the end result is right!

What is the end result of your startup process?

Regards!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
Ed_P
Contributor
Contributor
Posts: 3314
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: suspected timezone mismatch in /etc mouting on boot

Post#12 by Ed_P » 12 Aug 2016, 03:06

donald wrote:@ Ed
should be: less /var/log/messages.. :wink:
Thank you donald, that works. Don't know how to select a group of lines from the output though. Have to use leafpad.

Code: Select all

Aug 11 22:34:04 porteus init: Entering runlevel: 4
Aug 11 22:34:04 porteus acpid: starting up with netlink and the input layer
Aug 11 22:34:04 porteus acpid: 4 rules loaded
Aug 11 22:34:04 porteus acpid: waiting for events: event logging is off
Aug 11 22:34:05 porteus avahi-daemon[2354]: Found user 'avahi' (UID 214) and group 'avahi' (GID 214).
Aug 11 22:34:05 porteus avahi-daemon[2354]: Successfully dropped root privileges.
Aug 11 22:34:05 porteus avahi-daemon[2354]: avahi-daemon 0.6.31 starting up.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Successfully called chroot().
Aug 11 22:34:05 porteus avahi-daemon[2354]: Successfully dropped remaining capabilities.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Loading service file /services/sftp-ssh.service.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Loading service file /services/ssh.service.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Network interface enumeration completed.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Registering HINFO record with values 'X86_64'/'LINUX'.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Server startup complete. Host name is porteus.local. Local service cookie is 4277899120.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Service "porteus" (/services/ssh.service) successfully established.
Aug 11 22:34:05 porteus avahi-daemon[2354]: Service "porteus" (/services/sftp-ssh.service) successfully established.
Aug 11 22:34:05 porteus avahi-dnsconfd[2392]: Successfully connected to Avahi daemon.
Aug 11 22:34:06 porteus gpm[2398]: *** info [daemon/startup.c(136)]: 
Aug 11 22:34:06 porteus gpm[2398]: Started gpm successfully. Entered daemon mode.
Aug 11 22:34:06 porteus kernel: [   22.557351] NET: Registered protocol family 10
Aug 11 22:34:06 porteus NetworkManager[2418]: <info> NetworkManager (version 0.9.8.8) is starting...
Aug 11 22:34:06 porteus NetworkManager[2418]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Aug 11 22:34:06 porteus NetworkManager[2418]: <info> WEXT support is enabled
Aug 11 22:34:06 porteus NetworkManager[2418]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Aug 11 22:34:06 porteus NetworkManager[2418]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Aug 11 22:34:06 porteus LAPTOP-MODE: Laptop mode enabled, active [unchanged]
Aug 11 22:34:06 porteus dbus[1924]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Aug 11 22:34:07 porteus acpid: client connected from 2390[0:0]
Aug 11 22:34:07 porteus acpid: 1 client rule loaded
Aug 11 22:34:07 porteus polkitd[2445]: started daemon version 0.105 using authority implementation `local' version `0.105'
Aug 11 22:34:07 porteus dbus[1924]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing QuickMoose-8f2c7167-54b0-444b-b9df-5ceb39b3c324 ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     read connection 'QuickMoose'
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing SouthwestWiFi ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     error: File permissions (100755) or owner (0) were insecure
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing Residence_Inn ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     error: File permissions (100755) or owner (0) were insecure
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing QuickMoose ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     error: File permissions (100755) or owner (0) were insecure
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing Frontier3716 ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     error: File permissions (100755) or owner (0) were insecure
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing Cisco02318-guest ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     error: File permissions (100755) or owner (0) were insecure
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing ATWELL COTTAGE ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     error: File permissions (100755) or owner (0) were insecure
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile: parsing Frontier3716-e699b8fe-078f-4034-b220-6fb04a65c8d3 ... 
Aug 11 22:34:07 porteus NetworkManager[2418]:    keyfile:     read connection 'Frontier3716'
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> monitoring kernel firmware directory '/lib/firmware'.
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:15.3/0000:07:00.0/ieee80211/phy0/rfkill1) (driver wl)
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (platform driver acer-wmi)
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> WiFi hardware radio set enabled
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> WiFi enabled by radio killswitch; enabled by state file
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> WWAN enabled by radio killswitch; enabled by state file
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> WiMAX enabled by radio killswitch; enabled by state file
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> Networking is enabled by state file
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth0): carrier is OFF
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth0): new Ethernet device (driver: 'atl1c' ifindex: 2)
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth0): bringing up device.
Aug 11 22:34:07 porteus kernel: [   23.607253] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth0): preparing device.
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth0): deactivating device (reason 'managed') [2]
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:15.2/0000:06:00.0/net/eth0
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth1): using nl80211 for WiFi device control
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth1): new 802.11 WiFi device (driver: 'wl' ifindex: 3)
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/1
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth1): bringing up device.
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth1): preparing device.
Aug 11 22:34:07 porteus NetworkManager[2418]: <info> (eth1): deactivating device (reason 'managed') [2]
Aug 11 22:34:07 porteus dbus[1924]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Aug 11 22:34:08 porteus dbus[1924]: [system] Activating service name='org.freedesktop.ModemManager1' (using servicehelper)
Aug 11 22:34:08 porteus ModemManager[2458]: <info>  ModemManager (version 1.0.0) starting... 
Aug 11 22:34:08 porteus dbus[1924]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> wpa_supplicant started
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> (eth1) supports 1 scan SSIDs
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: starting -> ready
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> (eth1): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: ready -> disconnected
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> (eth1) supports 1 scan SSIDs
Aug 11 22:34:08 porteus dbus[1924]: [system] Successfully activated service 'org.freedesktop.ModemManager1'
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> ModemManager disappeared from bus
Aug 11 22:34:08 porteus NetworkManager[2418]: <info> ModemManager available in the bus
Aug 11 22:34:09 porteus avahi-daemon[2354]: Registering new address record for fe80::62d8:19ff:fe1a:a1fc on eth1.*.
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: disconnected -> inactive
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Auto-activating connection 'QuickMoose'.
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1) starting connection 'QuickMoose'
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> NetworkManager state is now CONNECTING
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1/wireless): connection 'QuickMoose' has security, and secrets exist.  No new secrets needed.
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Config: added 'ssid' value 'QuickMoose'
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Config: added 'scan_ssid' value '1'
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Config: added 'psk' value '<omitted>'
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> Config: set interface ap_scan to 1
Aug 11 22:34:09 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: inactive -> scanning
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: scanning -> associating
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: associating -> associated
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: associated -> 4-way handshake
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> (eth1): supplicant interface state: 4-way handshake -> completed
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'QuickMoose'.
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> (eth1): device state change: config -> ip-config (reason 'none') [50 70 0]
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> dhcpcd started with pid 2467
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Aug 11 22:34:10 porteus dhcpcd[2467]: version 6.0.5 starting
Aug 11 22:34:10 porteus NetworkManager[2418]: <info> (eth1): DHCPv4 state changed nbi -> preinit
Aug 11 22:34:10 porteus dhcpcd[2467]: eth1: soliciting an IPv6 router
Aug 11 22:34:10 porteus dhcpcd[2467]: eth1: rebinding lease of 192.168.200.212
Aug 11 22:34:10 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Aug 11 22:34:10 porteus dhcpcd[2467]: eth1: requesting DHCPv6 information
Aug 11 22:34:11 porteus NetworkManager[2418]: <info> (eth1): DHCPv4 state changed preinit -> (null)
Aug 11 22:34:12 porteus dbus[1924]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Aug 11 22:34:12 porteus avahi-daemon[2354]: Registering new address record for 2604:6000:1010:406b:62d8:19ff:fe1a:a1fc on eth1.*.
Aug 11 22:34:12 porteus avahi-daemon[2354]: Withdrawing address record for fe80::62d8:19ff:fe1a:a1fc on eth1.
Aug 11 22:34:12 porteus dbus[1924]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Aug 11 22:34:15 porteus dhcpcd[2467]: eth1: leased 192.168.200.212 for 86400 seconds
Aug 11 22:34:15 porteus dhcpcd[2467]: eth1: adding host route to 192.168.200.212 via 127.0.0.1
Aug 11 22:34:15 porteus dhcpcd[2467]: eth1: adding route to 192.168.200.0/24
Aug 11 22:34:15 porteus avahi-daemon[2354]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.200.212.
Aug 11 22:34:15 porteus avahi-daemon[2354]: New relevant interface eth1.IPv4 for mDNS.
Aug 11 22:34:15 porteus avahi-daemon[2354]: Registering new address record for 192.168.200.212 on eth1.IPv4.
Aug 11 22:34:15 porteus NetworkManager[2418]: <info> (eth1): DHCPv4 state changed (null) -> bound
Aug 11 22:34:15 porteus NetworkManager[2418]: <info>   address 192.168.200.212
Aug 11 22:34:15 porteus NetworkManager[2418]: <info>   prefix 24 (255.255.255.0)
Aug 11 22:34:15 porteus NetworkManager[2418]: <info>   gateway 192.168.200.1
Aug 11 22:34:15 porteus NetworkManager[2418]: <info>   hostname 'porteus'
Aug 11 22:34:15 porteus NetworkManager[2418]: <info>   nameserver '192.168.200.1'
Aug 11 22:34:15 porteus NetworkManager[2418]: <info>   domain name 'rochester.rr.com'
Aug 11 22:34:15 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Aug 11 22:34:15 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Commit) started...
Aug 11 22:34:15 porteus dhcpcd[2467]: eth1: removing IP address 192.168.200.212/24
Aug 11 22:34:15 porteus avahi-daemon[2354]: Withdrawing address record for 192.168.200.212 on eth1.
Aug 11 22:34:15 porteus avahi-daemon[2354]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.200.212.
Aug 11 22:34:15 porteus dhcpcd[2467]: eth1: removing route to 192.168.200.0/24
Aug 11 22:34:15 porteus avahi-daemon[2354]: Interface eth1.IPv4 no longer relevant for mDNS.
Aug 11 22:34:15 porteus avahi-daemon[2354]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.200.212.
Aug 11 22:34:15 porteus avahi-daemon[2354]: New relevant interface eth1.IPv4 for mDNS.
Aug 11 22:34:15 porteus avahi-daemon[2354]: Registering new address record for 192.168.200.212 on eth1.IPv4.
Aug 11 22:34:16 porteus NetworkManager[2418]: <info> (eth1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Aug 11 22:34:16 porteus NetworkManager[2418]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Commit) complete.
Aug 11 22:34:16 porteus NetworkManager[2418]: <info> (eth1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Aug 11 22:34:16 porteus NetworkManager[2418]: <info> NetworkManager state is now CONNECTED_GLOBAL
Aug 11 22:34:16 porteus NetworkManager[2418]: <info> Policy set 'QuickMoose' (eth1) as default for IPv4 routing and DNS.
Aug 11 22:34:17 porteus NetworkManager[2418]: <info> Activation (eth1) successful, device activated.
Aug 11 22:34:17 porteus dbus[1924]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Aug 11 22:34:17 porteus dbus[1924]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 11 22:34:28 porteus dbus[1924]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Aug 11 22:34:29 porteus dbus[1924]: [system] Successfully activated service 'org.freedesktop.UPower'
Aug 11 22:36:20 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Aug 11 22:36:20 porteus NetworkManager[2418]: <info> (eth1): DHCPv4 state changed bound -> (null)
Aug 11 22:38:36 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Aug 11 22:40:40 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Aug 11 22:41:59 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Aug 11 22:44:24 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Aug 11 22:46:01 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Aug 11 22:48:03 porteus dhcpcd[2467]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
I see no timing problem.

att do you have these updates in your system?

Code: Select all

guest@porteus:~$ ls /mnt/sda5/porteus3.0/Modules/00*
/mnt/sda5/porteus3.0/Modules/001-core_alldesktops-150124.xzm*
/mnt/sda5/porteus3.0/Modules/002-xorg_alldesktops-150119.xzm*
/mnt/sda5/porteus3.0/Modules/002-xorg_alldesktops-150126.xzm*
guest@porteus:~$ 
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1215
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: suspected timezone mismatch in /etc mouting on boot

Post#13 by donald » 12 Aug 2016, 08:56

@ att
Just an observation; because it is neither 3.0 nor 64 Bit.
However
I do not have any "different time" entries
(porteus 3.1 - no timezone settings in command line)

Code: Select all

Aug  6 02:36:19 porteus kernel: klogd 1.5.0, log source = /proc/kmsg started.
Aug  6 02:36:19 porteus kernel: [    0.000000] Initializing cgroup subsys cpu
Aug  6 02:36:19 porteus kernel: [    0.000000] Linux version 3.17.4-porteus (root@porteus) (gcc version 4.8.2 (GCC) ) #1 SMP PREEMPT Fri Dec 12 16:04:56 Local time zone must be set--
Aug  6 02:36:19 porteus kernel: [    0.000000] e820: BIOS-provided physical RAM map:
............
Aug  6 02:36:19 porteus kernel: [    0.000000] Kernel command line: quiet initrd=initrd.xz changes=/porteus  BOOT_IMAGE=vmlinuz
...........
Aug  6 02:36:19 porteus kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Aug  6 02:36:19 porteus kernel: [    0.000000] tsc: Detected 2599.956 MHz processor
Aug  6 02:36:19 porteus kernel: [    0.000000] tsc: Marking TSC unstable due to TSCs unsynchronized
............
Aug  6 02:36:19 porteus kernel: [    0.128034] Switched to clocksource hpet
............(1)
Aug  6 02:36:39 porteus acpid: starting up with netlink and the input layer
Aug  6 02:36:39 porteus acpid: 5 rules loaded
Aug  6 02:36:39 porteus acpid: waiting for events: event logging is off
...........
(1)
I don't have entries like:
mtp-probe..
Entering runlevel: 3

=======================================================
@ Ed
you can use cat /var/log/messages if you want.

Post Reply