I am using unprivi CTs for the first time.
Build: prox 5 ve
2x Dell R720 with 6xSAS drives each in hardware RAID10 running default local thin LVM storage. Dual e5-2640 CPUs, 64GB ram etc.
Findings:
Downloaded the centos 6 template (v20161207) via the prox ve. Did a yum update. Everything works fine, but I have 3 issues.
TTY issue is filling the log, see below:
Best fix I could find wast to blank tty.conf, is this dangerous? We have a tight firewall btw.
The VNC console also stopped working after the yum update. I switched to shell mode which works fine, less safe I guess. I know this is due to the TTY issue I cant seem to fix properly. This template works fine without these mentioned issues in normal privi mode. Tick the unprivi box and she moans. Maybe there is no fix for these issues because the apps will never have root privis. In that case the best fix maybe is to decrease the log level of the kernel? Any advice appreciated.
My other issue was just an observation, irqbalance moaned in the messages log so I just disabled it. I know this is all due to the new unprivi feature, but I would like to fix that TTY issue.
Build: prox 5 ve
2x Dell R720 with 6xSAS drives each in hardware RAID10 running default local thin LVM storage. Dual e5-2640 CPUs, 64GB ram etc.
Findings:
Downloaded the centos 6 template (v20161207) via the prox ve. Did a yum update. Everything works fine, but I have 3 issues.
TTY issue is filling the log, see below:
Code:
Aug 10 07:13:20 template1centos69ast11fbx12 init: tty (/dev/tty1) main process (320) terminated with status 1 Aug 10 07:13:20 template1centos69ast11fbx12 init: tty (/dev/tty1) main process ended, respawning Aug 10 07:13:20 template1centos69ast11fbx12 /sbin/mingetty[325]: tty1: vhangup() failed Aug 10 07:13:20 template1centos69ast11fbx12 init: tty (/dev/tty2) main process (322) terminated with status 1 Aug 10 07:13:20 template1centos69ast11fbx12 init: tty (/dev/tty2) main process ended, respawning Aug 10 07:13:20 template1centos69ast11fbx12 /sbin/mingetty[326]: tty2: vhangup() failed Aug 10 07:13:20 template1centos69ast11fbx12 init: tty (console) main process (323) terminated with status 1 Aug 10 07:13:20 template1centos69ast11fbx12 init: tty (console) main process ended, respawning Aug 10 07:13:20 template1centos69ast11fbx12 /sbin/mingetty[327]: console: vhangup() failed Aug 10 07:13:25 template1centos69ast11fbx12 init: tty (/dev/tty1) main process (325) terminated with status 1 Aug 10 07:13:25 template1centos69ast11fbx12 init: tty (/dev/tty1) main process ended, respawning Aug 10 07:13:25 template1centos69ast11fbx12 init: tty (/dev/tty2) main process (326) terminated with status 1 Aug 10 07:13:25 template1centos69ast11fbx12 init: tty (/dev/tty2) main process ended, respawning Aug 10 07:13:25 template1centos69ast11fbx12 /sbin/mingetty[328]: tty1: vhangup() failed Aug 10 07:13:25 template1centos69ast11fbx12 /sbin/mingetty[329]: tty2: vhangup() failed Aug 10 07:13:25 template1centos69ast11fbx12 init: tty (console) main process (327) terminated with status 1 Aug 10 07:13:25 template1centos69ast11fbx12 init: tty (console) main process ended, respawning Aug 10 07:13:25 template1centos69ast11fbx12 /sbin/mingetty[330]: console: vhangup() failed Aug 10 07:13:30 template1centos69ast11fbx12 init: tty (/dev/tty1) main process (328) terminated with status 1 Aug 10 07:13:30 template1centos69ast11fbx12 init: tty (/dev/tty1) main process ended, respawning Aug 10 07:13:30 template1centos69ast11fbx12 init: tty (/dev/tty2) main process (329) terminated with status 1 Aug 10 07:13:30 template1centos69ast11fbx12 init: tty (/dev/tty2) main process ended, respawning Aug 10 07:13:30 template1centos69ast11fbx12 /sbin/mingetty[331]: tty1: vhangup() failed Aug 10 07:13:30 template1centos69ast11fbx12 /sbin/mingetty[332]: tty2: vhangup() failed Aug 10 07:13:30 template1centos69ast11fbx12 init: tty (console) main process (330) terminated with status 1 Aug 10 07:13:30 template1centos69ast11fbx12 init: tty (console) main process ended, respawning Aug 10 07:13:30 template1centos69ast11fbx12 /sbin/mingetty[333]: console: vhangup() failedBest fix I could find wast to blank tty.conf, is this dangerous? We have a tight firewall btw.
Code:
cat /etc/init/tty.conf WARNING: terminal is not fully functional # tty - getty.conf (press RETURN) # # This service maintains a getty on the specified device. # # Do not edit this file directly. If you want to change the behaviour, # please create a file tty.override and put your changes there. #stop on runlevel [S016] #respawn #instance $TTY #exec /sbin/mingetty $TTY #usage 'tty TTY=/dev/ttyX - where X is console id'The VNC console also stopped working after the yum update. I switched to shell mode which works fine, less safe I guess. I know this is due to the TTY issue I cant seem to fix properly. This template works fine without these mentioned issues in normal privi mode. Tick the unprivi box and she moans. Maybe there is no fix for these issues because the apps will never have root privis. In that case the best fix maybe is to decrease the log level of the kernel? Any advice appreciated.
My other issue was just an observation, irqbalance moaned in the messages log so I just disabled it. I know this is all due to the new unprivi feature, but I would like to fix that TTY issue.
