This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Strange logs in /log/syslog.log file

The system is producing this output below every second as it appears in the advanced shell, it seems that login process is restarting continuously.

Feb 3 10:01:00 (none) daemon.info init: process '/bin/login' (pid 20205) exited. Scheduling for restart.

Feb 3 10:01:00 (none) daemon.info init: starting pid 20207, tty '/dev/ttyS0': '/bin/login'

Feb 3 10:01:01 (none) daemon.info init: process '/bin/login' (pid 20207) exited. Scheduling for restart.

Feb 3 10:01:01 (none) daemon.info init: starting pid 20208, tty '/dev/ttyS0': '/bin/login'

Feb 3 10:01:02 (none) daemon.info init: process '/bin/login' (pid 20208) exited. Scheduling for restart.

Feb 3 10:01:02 (none) daemon.info init: starting pid 20210, tty '/dev/ttyS0': '/bin/login'

This thread was automatically locked due to age.

0 hjherron6 over 8 years ago

I am seeing this as well.
Cancel
Vote Up 0 Vote Down

Cancel
0 lferrara over 8 years ago in reply to hjherron6

Hi all,

what version are you running?

I am on the latest one 16.05 MR1 and I do not see this issue.
Cancel
Vote Up 0 Vote Down

Cancel
0 George F.Kapaniris over 8 years ago in reply to lferrara

16.05 MR1 but the issue is there at least at 16.05 GA. I have reimaged the system to a new hardware so it is an issue for sure !
Cancel
Vote Up 0 Vote Down

Cancel
0 lferrara over 8 years ago in reply to George F.Kapaniris

George,

I advice you to open a ticke with the Support.

Let us know.

Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 George F.Kapaniris over 8 years ago in reply to lferrara

Indeed, this does not appear in all systems, I have checked another 2 systems with 16.05 MR1 and the issue is not there.
Cancel
Vote Up 0 Vote Down

Cancel
0 George F.Kapaniris over 8 years ago

I have found why the problem occurs. There was a serial port in the bios that was disabled and for some reason XG Firewall did not like this. After the port was enabled everything worked ok and there are no more complains in /log/syslog.log file from the system
Cancel
Vote Up 0 Vote Down

Cancel
0 DomNik over 8 years ago in reply to George F.Kapaniris

Hi all,

I have the same problem running the newest version 16.05.3 MR-3, which was installed just one week ago as a manual software installation in a KVM.

After I've ready jour post I've tried to add the installation CDROM drive "ide2" which I had removed after the installation back to the VM and did a reboot.

However the problem is still there, growing my logs continuously.

How can we investigate this problem any further?

Thanks and best regards

DomNik
Cancel
Vote Up 0 Vote Down

Cancel
0 Aditya Patel over 8 years ago in reply to DomNik

Hi Domnik,

I have reproduced the issue by disabling the Serial connection from BIOS. As I am using Vmware, I have gone to Bios Setup by selecting the option F2 and going to I/O configuration and disabled the serial connection which is usually set to auto by default.
Cancel
Vote Up 0 Vote Down

Cancel
0 George F.Kapaniris over 8 years ago in reply to Aditya Patel

Hello Aditya,

This bug I reported long time ago I think it is also driving the appliance to hang because of the high amount of logs; after I found the workaround the system does not hang anymore. Please fix it because many systems have the serial port working by default.
Cancel
Vote Up 0 Vote Down

Cancel
0 DomNik over 8 years ago in reply to George F.Kapaniris

Hi George, hi Aditya,

thank you for finding and explaining the workaround.

First I had the virtual cdrom drive in my mind, as this was my only change to the VM after the installation.

Later I found out that the problem exists since the very first start and googled a bit...

This is the workaround for KVM respectively Proxmox:

Logon to your hypervisor using SSH and change to the directory where the configuration files for the VMs are in:

cd /etc/pve/qemu-server

Add the following line to your <id>.conf file of the VM:

serial0: /dev/ttyS0

Stop and Start the VM and recheck the syslog. (I don't know if a reboot is working here.)

However the serial port forwarding seems to be experimental in Proxmox, so a fix for the original problem would be nice. :-)

Best Regards

Dom Nik
Cancel
Vote Up 0 Vote Down

Cancel