Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Steven Tardy 

> On Oct 30, 2016, at 7:31 PM, Paul R. Ganci  wrote:
> 
> Now the question is how did this happen.

I've seen something similar when installing a kernel if /etc/fstab didn't match 
df. Mkinitrd bombs out leaving the system unbootable. The rescue .iso/mkinitrd 
path you followed was the fastest way to get the system up.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci 


On 10/30/2016 03:05 PM, Eero Volotinen wrote:

so, Just chroot to mountpoint:

http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/

chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for 
documentation)

Thank you for the hint. The way I fixed this problem was to do this:

1.) Booted into linux rescue mode using the CentOS-7-x86_64-DVD-1511.iso
2.) chroot /mnt/sysimage
3.) Used nmtui to setup a network
4.) yum update (installed the 3.10.0-327-36.3.el7.x86_64 kernel)
5.) grub2-mkconfig -o /boot/grub2/grub.cfg 6.) yum reinstall 
kernel*-3.10.0-327-36.3.el7.x86_64


Step 5 was necessary because of a grubby error indicating that there was 
no suitable template. Step 6 was necessary because according to the 
googled page I found regarding step 5 indicated that the default kernel 
would not be that found in step 4. I probably could have skipped step 4 
and just done steps 5 and 6. But the VM is now up and running the latest 
kernel.


Now the question is how did this happen. My best guess is that the VM 
was unhappy when I booted the host while it was running. Is rebooting 
the host without shutting down guests first a risky thing to do?

--
Paul (ga...@nurdog.com)
Cell: (303)257-5208
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Eero Volotinen 
so, Just chroot to mountpoint:

http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/

chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for
documentation)

2016-10-30 22:57 GMT+02:00 Eero Volotinen :

> A bit hard to say. Try chrooting into environment and rebuilding initrd?
>
> --
> Eero
>
> 2016-10-30 22:53 GMT+02:00 Paul R. Ganci :
>
>> On 10/30/2016 12:26 PM, Paul R. Ganci wrote:
>>
>>> I am thinking of putting the CentOS iso out and then booting the
>>> VM into it just to poke around the file system. Otherwise my other option
>>> is to just clone a twin VM on another server and then just change the
>>> networking IPs/hostname. Anybody have any other ideas as to how to debug
>>> this problem?
>>>
>> So I booted off the CentOS-7-x86_64-DVD-1511.iso and everything looks
>> just fine:
>>
>> > df
>> Filesystem 1K-blocksUsed Available
>>  Use%   Mounted on
>> /dev/mapper/live-rw   20308999490221077781 47% /
>> devtmpfs   2004040  0 2004040
>>  0%   /dev
>> tmpfs 2023652  0 2023652
>>0%   /dev/shm
>> tmpfs 20236528520 2015132
>>  1%   /run
>> tmpfs 2023652  0 2023652
>>0%  /sys/fs/cgroup
>> /dev/sr1 4227724  4227724 0   100%
>> /run/install/repo
>> tmpfs 2023652  200 2023452
>>  1%  /tmp
>> /dev/mapper/centos-root  10799104  38941966904908 37%
>> /mnt/sysimage
>> /dev/vda1508588 143516 365072 29%
>> /mnt/sysimage/boot
>> tmpfs2023652   0 2023652
>>0%  /mnt/sysimage/dev/shm
>>
>> > ls /mnt/sysimage
>> bin   boot   dev   etc   home   lib   lib64   media   misc   mnt net
>>  opt   proc   rootrunsbin   srv   systmp   usr var
>>
>> > ls -l /mnt/sysimage/boot
>> total 109424
>> -rw-r--r--.1 root root   126431  Oct 10 23:18
>> config-3.10.0-327.36.2.el7.x86_64
>> drwxr-xr-x. 2 root root   26  Oct   2  2015  grub
>> drwx--.  6 root root 104  Oct 13 02:21  grub2
>> -rw-r--r--.1 root root   40655493  Apr   3  2015
>> initramfs-0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66.img
>> -rw---.1 root root   29666884 Oct 13  01:25
>> initramfs-3.10.0-327.36.2.el7.x86_64.img
>> -rw---.1 root root   18119089  Oct 13 02:20
>> initramfs-3.10.0-327.36.2.el7.x86_64kdump.img
>> -rw-r--r--.1 root root   10190975  Dec 19  2015 initrd-plymouth.img
>> -rw-r--r--.1 root root  252739  Oct  10 23:20
>> symvers-3.10.0-327.36.2.el7.x86_64.gz
>> -rw---.1 root root2965270  Oct  10 23:18
>> System.map-3.10.0-327.36.2.el7.x86_64
>> -rwxr-xr-x.   1 root root4902656  Apr3  2015
>> vmlinuz0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66
>> -rwxr-xr-x.   1 root root5157936   Oct  10 23:18
>> vmlinuz-3.10.0-327.36.2.el7.x86_64
>>
>> So the CentOS DVD iso in linux rescue mode shows that everything is there
>> and can be mounted. I guess that means somehow either grub itself is
>> corrupted or one of the boot images. So is there a way for me to generate a
>> new initrd while booted in linux resuce mode or will re-installing grub
>> help? How would I attempt re-installing grub while booted in linux rescue
>> mode?
>>
>> --
>> Paul (ga...@nurdog.com)
>> Cell: (303)257-5208
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Eero Volotinen 
A bit hard to say. Try chrooting into environment and rebuilding initrd?

--
Eero

2016-10-30 22:53 GMT+02:00 Paul R. Ganci :

> On 10/30/2016 12:26 PM, Paul R. Ganci wrote:
>
>> I am thinking of putting the CentOS iso out and then booting the VM
>> into it just to poke around the file system. Otherwise my other option is
>> to just clone a twin VM on another server and then just change the
>> networking IPs/hostname. Anybody have any other ideas as to how to debug
>> this problem?
>>
> So I booted off the CentOS-7-x86_64-DVD-1511.iso and everything looks just
> fine:
>
> > df
> Filesystem 1K-blocksUsed Available   Use%
>  Mounted on
> /dev/mapper/live-rw   20308999490221077781 47% /
> devtmpfs   2004040  0 2004040
>  0%   /dev
> tmpfs 2023652  0 2023652
>  0%   /dev/shm
> tmpfs 20236528520 2015132
>  1%   /run
> tmpfs 2023652  0 2023652
>  0%  /sys/fs/cgroup
> /dev/sr1 4227724  4227724 0   100%
> /run/install/repo
> tmpfs 2023652  200 2023452
>  1%  /tmp
> /dev/mapper/centos-root  10799104  38941966904908 37% /mnt/sysimage
> /dev/vda1508588 143516 365072 29%
> /mnt/sysimage/boot
> tmpfs2023652   0 2023652
>  0%  /mnt/sysimage/dev/shm
>
> > ls /mnt/sysimage
> bin   boot   dev   etc   home   lib   lib64   media   misc   mnt net
>  opt   proc   rootrunsbin   srv   systmp   usr var
>
> > ls -l /mnt/sysimage/boot
> total 109424
> -rw-r--r--.1 root root   126431  Oct 10 23:18
> config-3.10.0-327.36.2.el7.x86_64
> drwxr-xr-x. 2 root root   26  Oct   2  2015  grub
> drwx--.  6 root root 104  Oct 13 02:21  grub2
> -rw-r--r--.1 root root   40655493  Apr   3  2015
> initramfs-0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66.img
> -rw---.1 root root   29666884 Oct 13  01:25
> initramfs-3.10.0-327.36.2.el7.x86_64.img
> -rw---.1 root root   18119089  Oct 13 02:20
> initramfs-3.10.0-327.36.2.el7.x86_64kdump.img
> -rw-r--r--.1 root root   10190975  Dec 19  2015 initrd-plymouth.img
> -rw-r--r--.1 root root  252739  Oct  10 23:20
> symvers-3.10.0-327.36.2.el7.x86_64.gz
> -rw---.1 root root2965270  Oct  10 23:18
> System.map-3.10.0-327.36.2.el7.x86_64
> -rwxr-xr-x.   1 root root4902656  Apr3  2015
> vmlinuz0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66
> -rwxr-xr-x.   1 root root5157936   Oct  10 23:18
> vmlinuz-3.10.0-327.36.2.el7.x86_64
>
> So the CentOS DVD iso in linux rescue mode shows that everything is there
> and can be mounted. I guess that means somehow either grub itself is
> corrupted or one of the boot images. So is there a way for me to generate a
> new initrd while booted in linux resuce mode or will re-installing grub
> help? How would I attempt re-installing grub while booted in linux rescue
> mode?
>
> --
> Paul (ga...@nurdog.com)
> Cell: (303)257-5208
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci 

On 10/30/2016 12:26 PM, Paul R. Ganci wrote:
I am thinking of putting the CentOS iso out and then booting the 
VM into it just to poke around the file system. Otherwise my other 
option is to just clone a twin VM on another server and then just 
change the networking IPs/hostname. Anybody have any other ideas as to 
how to debug this problem?
So I booted off the CentOS-7-x86_64-DVD-1511.iso and everything looks 
just fine:


> df
Filesystem 1K-blocksUsed Available   
Use%   Mounted on

/dev/mapper/live-rw   20308999490221077781 47% /
devtmpfs   2004040  0 2004040   
0%   /dev
tmpfs 2023652  0 
2023652   0%   /dev/shm
tmpfs 20236528520 2015132   
1%   /run
tmpfs 2023652  0 
2023652   0%  /sys/fs/cgroup
/dev/sr1 4227724  4227724 0   100%  
/run/install/repo
tmpfs 2023652  200 2023452   
1%  /tmp

/dev/mapper/centos-root  10799104  38941966904908 37% /mnt/sysimage
/dev/vda1508588 143516 365072 29%  
/mnt/sysimage/boot
tmpfs2023652   0 
2023652   0%  /mnt/sysimage/dev/shm


> ls /mnt/sysimage
bin   boot   dev   etc   home   lib   lib64   media   misc   mnt net   
opt   proc   rootrunsbin   srv   systmp   usr var


> ls -l /mnt/sysimage/boot
total 109424
-rw-r--r--.1 root root   126431  Oct 10 23:18 
config-3.10.0-327.36.2.el7.x86_64

drwxr-xr-x. 2 root root   26  Oct   2  2015  grub
drwx--.  6 root root 104  Oct 13 02:21  grub2
-rw-r--r--.1 root root   40655493  Apr   3  2015 
initramfs-0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66.img
-rw---.1 root root   29666884 Oct 13  01:25 
initramfs-3.10.0-327.36.2.el7.x86_64.img
-rw---.1 root root   18119089  Oct 13 02:20 
initramfs-3.10.0-327.36.2.el7.x86_64kdump.img

-rw-r--r--.1 root root   10190975  Dec 19  2015 initrd-plymouth.img
-rw-r--r--.1 root root  252739  Oct  10 23:20 
symvers-3.10.0-327.36.2.el7.x86_64.gz
-rw---.1 root root2965270  Oct  10 23:18 
System.map-3.10.0-327.36.2.el7.x86_64
-rwxr-xr-x.   1 root root4902656  Apr3  2015 
vmlinuz0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66
-rwxr-xr-x.   1 root root5157936   Oct  10 23:18 
vmlinuz-3.10.0-327.36.2.el7.x86_64


So the CentOS DVD iso in linux rescue mode shows that everything is 
there and can be mounted. I guess that means somehow either grub itself 
is corrupted or one of the boot images. So is there a way for me to 
generate a new initrd while booted in linux resuce mode or will 
re-installing grub help? How would I attempt re-installing grub while 
booted in linux rescue mode?

--
Paul (ga...@nurdog.com)
Cell: (303)257-5208
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Eero Volotinen 
You could mount image ja rebuild initrd.

Eero

2016-10-30 20:26 GMT+02:00 Paul R. Ganci :

> On 10/30/2016 07:33 AM, FrancisM wrote:
>
>> Any error in your host logs?
>>
> Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu,
> /var/log/libvirt/lxc & /var/log/qemu-ga. The /var/log/libvirt/lxc &
> /var/log/qemu-ga were empty. The /var/log/libvirt/qemu directory had a log
> file of interest Outgoing-CentOS-7-VM.log but nothing in it that tells me
> anything obvious.
>
>  2016-10-30 06:40:09.764+: shutting down
> 2016-10-30 06:40:16.926+: starting up libvirt version: 1.2.17,
> package: 13.el7_2.5 (CentOS BuildSystem ,
> 2016-06-23-14:23:27, worker1.bsys.centos.org), qemu version: 1.5.3
> (qemu-kvm-1.5.3-105.el7_2.7)
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name Outgoing-CentOS-7-VM -S
> -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu Penryn -m 4096
> -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid
> 6494b5d9-8adc-4f66-b0cf-4c19a0f6ab66 -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Outg
> oing-CentOS-7-VM/monitor.sock,server,nowait -mon
> chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew
> -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global
> PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device
> ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device
> ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
> -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1
> -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2
> -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive
> file=/vm-images/centos7.0.qcow2,if=none,id=drive-virtio-disk0,format=qcow2
> -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virti
> o-disk0,id=virtio-disk0,bootindex=1 -drive 
> if=none,id=drive-ide0-0-0,readonly=on,format=raw
> -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev
> tap,fd=25,id=hostnet0,vhost=on,vhostfd=27 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:7b:a5:c2,bus=pci.0,addr=0x3
> -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
> -chardev spicevmc,id=charchannel0,name=vdagent -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel
> 0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice
> port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl
> -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864
> -global qxl-vga.vgamem_mb=16 -device intel-hda,id=sound0,bus=pci.0,addr=0x4
> -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev
> spicevmc,id=charredir0,name=usbredir -device
> usb-redir,chardev=charredir0,id=redir0 -chardev
> spicevmc,id=charredir1,name=usbredir -device
> usb-redir,chardev=charredir1,id=redir1 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
> char device redirected to /dev/pts/1 (label charserial0)
> main_channel_link: add main channel client
> main_channel_handle_parsed: net test: latency 0.226000 ms, bitrate
> 37925925925 bps (36168.981481 Mbps)
> red_dispatcher_set_cursor_peer:
> inputs_connect: inputs channel client create
> red_peer_receive: Connection reset by peer
> red_channel_client_disconnect: rcc=0x7f2b11db6000 (channel=0x7f2b115b6600
> type=2 id=0)
> red_peer_receive: Connection reset by peer
> red_channel_client_disconnect: rcc=0x7f2b11d71000 (channel=0x7f2b10faa000
> type=3 id=0)
> red_channel_client_disconnect: rcc=0x7f2b11d8d000 (channel=0x7f2b10f8c4e0
> type=9 id=0)
> red_channel_client_disconnect: rcc=0x7f2b11d88000 (channel=0x7f2b10f8c680
> type=9 id=1)
> red_channel_client_disconnect: rcc=0x7f2b11a33000 (channel=0x7f2b10fa2000
> type=1 id=0)
> main_channel_client_on_disconnect: rcc=0x7f2b11a33000
> red_client_destroy: destroy client 0x7f2b10f2fd00 with #channels=4
> red_dispatcher_disconnect_cursor_peer:
> red_channel_client_disconnect: rcc=0x7f2b11d6c000 (channel=0x7f2b11938000
> type=4 id=0)
> red_dispatcher_disconnect_display_peer
>
> I reboot the host while the guests were running. Is it possible the root
> file system was corrupted during the host reboot? I am thinking of putting
> the CentOS iso out and then booting the VM into it just to poke around the
> file system. Otherwise my other option is to just clone a twin VM on
> another server and then just change the networking IPs/hostname. Anybody
> have any other ideas as to how to debug this problem?
> --
> Paul (ga...@nurdog.com)
> Cell: (303)257-5208
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci 

On 10/30/2016 07:33 AM, FrancisM wrote:

Any error in your host logs?
Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu, 
/var/log/libvirt/lxc & /var/log/qemu-ga. The /var/log/libvirt/lxc & 
/var/log/qemu-ga were empty. The /var/log/libvirt/qemu directory had a 
log file of interest Outgoing-CentOS-7-VM.log but nothing in it that 
tells me anything obvious.


 2016-10-30 06:40:09.764+: shutting down
2016-10-30 06:40:16.926+: starting up libvirt version: 1.2.17, 
package: 13.el7_2.5 (CentOS BuildSystem , 
2016-06-23-14:23:27, worker1.bsys.centos.org), qemu version: 1.5.3 
(qemu-kvm-1.5.3-105.el7_2.7)
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin 
QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name Outgoing-CentOS-7-VM -S 
-machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu Penryn -m 4096 
-realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 
6494b5d9-8adc-4f66-b0cf-4c19a0f6ab66 -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Outgoing-CentOS-7-VM/monitor.sock,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc 
base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet 
-no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 
-boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 
-device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 
-device 
ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 
-device 
ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive 
file=/vm-images/centos7.0.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 
-device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 
-drive if=none,id=drive-ide0-0-0,readonly=on,format=raw -device 
ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev 
tap,fd=25,id=hostnet0,vhost=on,vhostfd=27 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:7b:a5:c2,bus=pci.0,addr=0x3 
-chardev pty,id=charserial0 -device 
isa-serial,chardev=charserial0,id=serial0 -chardev 
spicevmc,id=charchannel0,name=vdagent -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 
-device usb-tablet,id=input0 -spice 
port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga 
qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 
-global qxl-vga.vgamem_mb=16 -device 
intel-hda,id=sound0,bus=pci.0,addr=0x4 -device 
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev 
spicevmc,id=charredir0,name=usbredir -device 
usb-redir,chardev=charredir0,id=redir0 -chardev 
spicevmc,id=charredir1,name=usbredir -device 
usb-redir,chardev=charredir1,id=redir1 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on

char device redirected to /dev/pts/1 (label charserial0)
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 0.226000 ms, bitrate 
37925925925 bps (36168.981481 Mbps)

red_dispatcher_set_cursor_peer:
inputs_connect: inputs channel client create
red_peer_receive: Connection reset by peer
red_channel_client_disconnect: rcc=0x7f2b11db6000 
(channel=0x7f2b115b6600 type=2 id=0)

red_peer_receive: Connection reset by peer
red_channel_client_disconnect: rcc=0x7f2b11d71000 
(channel=0x7f2b10faa000 type=3 id=0)
red_channel_client_disconnect: rcc=0x7f2b11d8d000 
(channel=0x7f2b10f8c4e0 type=9 id=0)
red_channel_client_disconnect: rcc=0x7f2b11d88000 
(channel=0x7f2b10f8c680 type=9 id=1)
red_channel_client_disconnect: rcc=0x7f2b11a33000 
(channel=0x7f2b10fa2000 type=1 id=0)

main_channel_client_on_disconnect: rcc=0x7f2b11a33000
red_client_destroy: destroy client 0x7f2b10f2fd00 with #channels=4
red_dispatcher_disconnect_cursor_peer:
red_channel_client_disconnect: rcc=0x7f2b11d6c000 
(channel=0x7f2b11938000 type=4 id=0)

red_dispatcher_disconnect_display_peer

I reboot the host while the guests were running. Is it possible the root 
file system was corrupted during the host reboot? I am thinking of 
putting the CentOS iso out and then booting the VM into it just to poke 
around the file system. Otherwise my other option is to just clone a 
twin VM on another server and then just change the networking 
IPs/hostname. Anybody have any other ideas as to how to debug this problem?

--
Paul (ga...@nurdog.com)
Cell: (303)257-5208
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci 


On 10/30/2016 06:57 AM, Steven Tardy wrote:

On Oct 30, 2016, at 3:27 AM, Paul R. Ganci  wrote:

grub> set root=(hd0,msdos2)
grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/
grub> initrd initrd-plymouth.img
grub> boot

Try the initrd matching the kernel
That is what I thought was strange... there is no matching initrd. The 
only one there was the one I tried. I checked all the working systems 
both hosts and guests and they all just have a initrd-plymouth.img.

--
Paul (ga...@nurdog.com)
Cell: (303)257-5208
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread FrancisM 
Any error in your host logs?

On Sunday, 30 October 2016, Steven Tardy  wrote:

>
> > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci  > wrote:
> >
> > grub> set root=(hd0,msdos2)
> > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64
> root=(hd0,msdos2)/
> > grub> initrd initrd-plymouth.img
> > grub> boot
>
> Try the initrd matching the kernel?
> ___
> CentOS mailing list
> CentOS@centos.org 
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Steven Tardy 

> On Oct 30, 2016, at 3:27 AM, Paul R. Ganci  wrote:
> 
> grub> set root=(hd0,msdos2)
> grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/
> grub> initrd initrd-plymouth.img
> grub> boot

Try the initrd matching the kernel?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disk near failure

2016-10-30 Thread Leonard den Ottolander 
Hi Yamaban,

On Sun, 2016-10-30 at 11:10 +0100, Leonard den Ottolander wrote:
> Still no argument to replace an existing working one... And as I asked
> Valeri, can you please provide us with links indicating the poor quality
> of Corsair SSDs (in general)?

Well never mind that request, very interesting to read your lectures
later in this thread :) .

Regards,
Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disk near failure

2016-10-30 Thread Leonard den Ottolander 
Hello Yamaban,

On Thu, 2016-10-27 at 19:38 +0200, Yamaban wrote:
> For my personal use I would replace that Drive asap.
> - There is no warranty for it anymore (time since buy)

I fail to see how that is relevant... If you lose your data because of a
failing disk you lose your data. Whether or not you get a replacement
drive does not change that fact. The length of a warranty might be an
indication of the expected life of a product, but it says nothing about
the state of one individual drive.

> - You can't buy it new anymore (discontinued)

Again, relevance?

> - There are more reliable drives available.

Still no argument to replace an existing working one... And as I asked
Valeri, can you please provide us with links indicating the poor quality
of Corsair SSDs (in general)?

I do not know how SSDs fail, but when regular HDs start to fail you
usually have some time to get a replacement before they fail altogether.
I would expect the number of reallocated sectors to increase, but still
have a little time to replace the disk once that happens. And supposing
the disk actually does store the number of "retired" blocks this disk
seems fine:

> >  5 Retired_Block_Count 0x0033   100   100   003Pre-fail Always  -  0

Regards,
Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disk near failure

2016-10-30 Thread Leonard den Ottolander 
Hello Valeri,

On Fri, 2016-10-28 at 09:28 -0500, Valeri Galtsev wrote:
> Amazing. He suggested you definitely reliable drive (Samsung). Reliable in
> my boot too. You ask his opinion about yet another Corsair. One by Corsair
> failed on you already.

It did not. He asked whether it did but there is no indication it is
near failure and definitely hasn't failed yet.

>  So, you should have better knowledge about
> Corsair's SSD reliability, right?

Can you provide us with links indicating the unreliability of (any or
all) Corsair SSDs? I've had IBM Deskstars failing on me prematurely.
Does that disqualify IBM as a producer of hard drives? (Ok, they are no
longer in that business, but that's not the point I'm trying to make.)
And not so long ago I had problems with my internet provider buying a
batch of lousy Seagates that kept failing. Does that disqualify all
Seagate disks?

Regards,
Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread John R Pierce 

On 10/30/2016 12:47 AM, Ned Slider wrote:

On 30/10/16 07:11, Hadi Motamedi wrote:

But the site is far remote and having alert on battery exhaustion can no
longer help . As I said before , I am suspicious if it comes from 
frequent
power cuts so seeking some means to distinguish it among the system 
logs.


Your UPS should be capable of logging to /var/log/messages and should 
also be capable of powering down the system cleanly when the battery 
reaches a predetermined critical level (either run time remaining or 
percentage charge), so there shouldn't be any uninitiated shutdowns. 
The UPS logs should tell you exactly how many power outages you are 
getting together with how long each one lasts. It sounds like you 
haven't configured your UPS.


if its a proper enterprise/server grade commercial UPS, you should be 
able to monitor the charge state of the battery via the USB network 
interface...  I don't know what sort of UPS this is, and I've seen some 
pictures of some awful things in the third world that use a charger 
module, and a bunch of old car batteries on the floor, and an inverter,  
running whole households during the regular afternoon brownouts.   I 
don't think those sorts of things *have* network monitoring, but 
enterprise grade UPS's like newer SmartUPS, Eaton PowerWare, etc DO have 
this ability.APC tend to be worse at this than most of the better 
alternatives like Eaton.


if this UPS *does* have any sort of thing that will give you battery 
state information, use NUT, the Network UPS Tool, on linux, and if 
you're dealing with a homebrew UPS, build your own module that can 
monitor that voltage.   I would use NUT initiate an OS shutdown when you 
get to 20% battery charge state, which is around 12.0VDC (fully charged 
12V lead acid battery is 12.6VDC, on the AC powered charger, its more 
like 13.8-14.1V). NUT is quite powerful, and very flexible.   one 
server could monitor the UPS (maybe even via using a USB digital volt 
meter module connected directly to the batteries), and that master NUT 
node could tell all the other nodes/systems to shutdown, too.


Letting this sort of homebrew UPS fully run down the batteries to 
totally dead shortens the batteries life. if you could shut the 
systems AND the UPS off at before the batteries are totally run down, 
they'll last a lot longer.


if this UPS is the homebrew third world bodge I described, you could 
pretty easily build a NUT master w/ a raspberry pi and a ADC 'hat'






--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Hadi Motamedi 
Thank you very much for your help. I have received plentiful helpful
messages . Please consider this case as solved.
Thank you again

On Sun, Oct 30, 2016 at 12:47 AM, Ned Slider  wrote:

> On 30/10/16 07:11, Hadi Motamedi wrote:
>
>> But the site is far remote and having alert on battery exhaustion can no
>> longer help . As I said before , I am suspicious if it comes from frequent
>> power cuts so seeking some means to distinguish it among the system logs.
>> Thank you in advance
>>
>>
>>
> Your UPS should be capable of logging to /var/log/messages and should also
> be capable of powering down the system cleanly when the battery reaches a
> predetermined critical level (either run time remaining or percentage
> charge), so there shouldn't be any uninitiated shutdowns. The UPS logs
> should tell you exactly how many power outages you are getting together
> with how long each one lasts. It sounds like you haven't configured your
> UPS.
>
>
>
>
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Ned Slider 

On 30/10/16 07:11, Hadi Motamedi wrote:

But the site is far remote and having alert on battery exhaustion can no
longer help . As I said before , I am suspicious if it comes from frequent
power cuts so seeking some means to distinguish it among the system logs.
Thank you in advance




Your UPS should be capable of logging to /var/log/messages and should 
also be capable of powering down the system cleanly when the battery 
reaches a predetermined critical level (either run time remaining or 
percentage charge), so there shouldn't be any uninitiated shutdowns. The 
UPS logs should tell you exactly how many power outages you are getting 
together with how long each one lasts. It sounds like you haven't 
configured your UPS.







___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

2016-10-30 Thread Paul R. Ganci 
I have something very strange that occurred. After updating the kernel 
on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7 
guest VMs will no longer boot... it just stops at the grub prompt (a 
second VM functions just fine). I have no idea why this problem occurred 
and have been unable to fix it. On google I have found several 
suggestions as to how to repair grub but so far none have worked. What I 
have found so far is this:


grub> ls
(hd0) (hd0,msdos2) (hd0,msdos1)

grub> ls -l (hd0,1) (hd0,msdos2) (hd0,msdos1)
 Partition hd0,1: Filesystem type xfs, UUID
250008ab-9fde-4892-a8b7-a38882b1a1448 - Partition start at 1024KiB - 
Total size

512000Kib
 Partition hd0,msdos2: No known filesystem detected - 
Partition start at

513024KiB - Total size 12069888KiB
 Partition hd0,msdos1: Filesystem type xfs, UUID
250008ab-9fde-4892-a8b7-a38882b1a1448 - Partition start at 1024KiB - 
Total size

512000Kib

So it appears that (hd0,1) and (hd0,msdos1) are the same partition 
containing the boot directory contents


grub> set root=(hd0,1)
grub> ls -l /
DIR20151002231139 grub/
DIR20161013022100 grub2/
10190975 20151219235512 initrd-plymouth.img
4065549320150403032637 
initramfs-0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66.img
4902656  20150403032703 
vmlinuz0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66

252739 20161010232025 symvers-3.10.0-327.36.2.el7.x86_64.gz
29666884 20161013012551 initramfs-3.10.0-327.36.2.el7.x86_64.img
2965270   20161010231818 System.map-3.10.0-327.36.2.el7.x86_64
126431 20161010231818 config-3.10.0-327.36.2.el7.x86_64
5157936   20161010231819 vmlinuz-3.10.0-327.36.2.el7.x86_64
18119089 20161013022032 
initramfs-3.10.0-327.36.2.el7.x86_64kdump.img


Is that (hd0,msdos2) the root partition? If is, has it become corrupted 
somehow? Can I get this system to boot somehow so that I might fix the 
grub configuration? So far I have tried something along these lines with 
out success:


grub> set root=(hd0,msdos2)
grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/
grub> initrd initrd-plymouth.img
grub> boot

I just get this error:
[ 2.128131] No filesystem could mount root, tried:
[ 2.129038] Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown-block(1,0)
[ 2.130537] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
3.10.0-327.36.2.el7.x86_64 #1

[ 2.132017] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011

{remainder of stack dump}

Does anyone have any ideas as to

1.) How to fix the problem?
2.) Why the problem occurred in the first place?
3.) How to go about debugging the problem?

I would really like to know how this problem could have occurred on the 
1 VM but the Host and 2nd Guest are just fine?


Thanks for your help.

--
Paul (ga...@nurdog.com)
Cell: (303)257-5208
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Hadi Motamedi 
Thank you very much for your time . I got the point and it is a very
helpful message .
Thank you again


On Sun, Oct 30, 2016 at 12:19 AM, John R Pierce  wrote:

> On 10/30/2016 12:02 AM, Hadi Motamedi wrote:
>
>> Thank you very much for your reply . So you mean under the
>> /var/log/messages it is distinguishable that which logs come from operator
>> initiated reboot and which ones come from sudden power cut and then
>> booting
>> from scratch when power resumed ? Am I correct ?
>>
>
> if the power fails without warning, there will be no orderly shutdown of
> system services prior to the startup sequence
>
>
>
> --
> john r pierce, recycling bits in santa cruz
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread John R Pierce 

On 10/30/2016 12:02 AM, Hadi Motamedi wrote:

Thank you very much for your reply . So you mean under the
/var/log/messages it is distinguishable that which logs come from operator
initiated reboot and which ones come from sudden power cut and then booting
from scratch when power resumed ? Am I correct ?


if the power fails without warning, there will be no orderly shutdown of 
system services prior to the startup sequence



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Hadi Motamedi 
But the site is far remote and having alert on battery exhaustion can no
longer help . As I said before , I am suspicious if it comes from frequent
power cuts so seeking some means to distinguish it among the system logs.
Thank you in advance


On Sun, Oct 30, 2016 at 12:08 AM, Mike Mohr  wrote:

> If your battery backup can handle 2 hours of runtime then it almost
> certainly has a network management interface. Why aren't you using it to
> send alerts?
>
> On Oct 30, 2016 12:05 AM, "Hadi Motamedi"  wrote:
>
> > Thank you for your reply. You are correct and the ups is present there
> but
> > the battery charger can no longer bear power cuts more than two hours so
> I
> > need some means to distinguish frequent power cuts there among the system
> > logs.
> >
> > On Sun, Oct 30, 2016 at 12:02 AM, Eero Volotinen 
> > wrote:
> >
> > > you could use smart ups and connect information from it to system, so
> it
> > > can shutdown system in clean way.
> > >
> > > Eero
> > >
> > > 2016-10-30 7:12 GMT+02:00 Hadi Motamedi :
> > >
> > > > Dear All
> > > > I am using a centos server for cdr billing and mediation device on a
> > > remote
> > > > network. I am experiencing problem that I am suspicious it comes from
> > > main
> > > > supply power cut at the remote site. The power supply to the remote
> > site
> > > > comes from battery charger that will be automatically switched in
> > circuit
> > > > under main supply power cut but cannot provide adequate power for
> more
> > > than
> > > > 2 hours . I am suspicious that the remote system is suffering from
> many
> > > > frequent main supply power cut . Can you please do me favor and let
> me
> > > know
> > > > if there is any log on my centos server that I can check to see if
> > there
> > > > would be many frequent power cut there ?
> > > > Thank you for your time
> > > > ___
> > > > CentOS mailing list
> > > > CentOS@centos.org
> > > > https://lists.centos.org/mailman/listinfo/centos
> > > >
> > > ___
> > > CentOS mailing list
> > > CentOS@centos.org
> > > https://lists.centos.org/mailman/listinfo/centos
> > >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Mike Mohr 
If your battery backup can handle 2 hours of runtime then it almost
certainly has a network management interface. Why aren't you using it to
send alerts?

On Oct 30, 2016 12:05 AM, "Hadi Motamedi"  wrote:

> Thank you for your reply. You are correct and the ups is present there but
> the battery charger can no longer bear power cuts more than two hours so I
> need some means to distinguish frequent power cuts there among the system
> logs.
>
> On Sun, Oct 30, 2016 at 12:02 AM, Eero Volotinen 
> wrote:
>
> > you could use smart ups and connect information from it to system, so it
> > can shutdown system in clean way.
> >
> > Eero
> >
> > 2016-10-30 7:12 GMT+02:00 Hadi Motamedi :
> >
> > > Dear All
> > > I am using a centos server for cdr billing and mediation device on a
> > remote
> > > network. I am experiencing problem that I am suspicious it comes from
> > main
> > > supply power cut at the remote site. The power supply to the remote
> site
> > > comes from battery charger that will be automatically switched in
> circuit
> > > under main supply power cut but cannot provide adequate power for more
> > than
> > > 2 hours . I am suspicious that the remote system is suffering from many
> > > frequent main supply power cut . Can you please do me favor and let me
> > know
> > > if there is any log on my centos server that I can check to see if
> there
> > > would be many frequent power cut there ?
> > > Thank you for your time
> > > ___
> > > CentOS mailing list
> > > CentOS@centos.org
> > > https://lists.centos.org/mailman/listinfo/centos
> > >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Hadi Motamedi 
Thank you for your reply. You are correct and the ups is present there but
the battery charger can no longer bear power cuts more than two hours so I
need some means to distinguish frequent power cuts there among the system
logs.

On Sun, Oct 30, 2016 at 12:02 AM, Eero Volotinen 
wrote:

> you could use smart ups and connect information from it to system, so it
> can shutdown system in clean way.
>
> Eero
>
> 2016-10-30 7:12 GMT+02:00 Hadi Motamedi :
>
> > Dear All
> > I am using a centos server for cdr billing and mediation device on a
> remote
> > network. I am experiencing problem that I am suspicious it comes from
> main
> > supply power cut at the remote site. The power supply to the remote site
> > comes from battery charger that will be automatically switched in circuit
> > under main supply power cut but cannot provide adequate power for more
> than
> > 2 hours . I am suspicious that the remote system is suffering from many
> > frequent main supply power cut . Can you please do me favor and let me
> know
> > if there is any log on my centos server that I can check to see if there
> > would be many frequent power cut there ?
> > Thank you for your time
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Hadi Motamedi 
Thank you very much for your reply . So you mean under the
/var/log/messages it is distinguishable that which logs come from operator
initiated reboot and which ones come from sudden power cut and then booting
from scratch when power resumed ? Am I correct ?


On Sat, Oct 29, 2016 at 11:44 PM, John R Pierce  wrote:

> On 10/29/2016 10:12 PM, Hadi Motamedi wrote:
>
>> I am using a centos server for cdr billing and mediation device on a
>> remote
>> network. I am experiencing problem that I am suspicious it comes from main
>> supply power cut at the remote site. The power supply to the remote site
>> comes from battery charger that will be automatically switched in circuit
>> under main supply power cut but cannot provide adequate power for more
>> than
>> 2 hours . I am suspicious that the remote system is suffering from many
>> frequent main supply power cut . Can you please do me favor and let me
>> know
>> if there is any log on my centos server that I can check to see if there
>> would be many frequent power cut there ?
>>
>
> look at /var/log/messages for reboots without shutdowns.
>
> centos 6 linux boot starts logging something like...
>
> Oct 25 15:01:25 new kernel: imklog 5.8.10, log source = /proc/kmsg started.
> Oct 25 15:01:25 new rsyslogd: [origin software="rsyslogd"
> swVersion="5.8.10" x-pid="2740" x-info="http://www.rsyslog.com;] start
> Oct 25 15:01:25 new kernel: Initializing cgroup subsys cpuset
> Oct 25 15:01:25 new kernel: Initializing cgroup subsys cpu
> Oct 25 15:01:25 new kernel: Linux version 2.6.32-642.6.1.el6.x86_64 (
> mockbu...@worker1.bsys.centos.org) (gcc version 4.4.7 20120313 (Red Hat
> 4.4.7-17) (GCC) ) #1 SMP Wed Oct 5 00:36:12 UTC 2016
>
>
> followed by tons more about all the stuff starting up
>
>
> when its properly shutdown, you'd see something like this after everything
> has stopped
>
> Oct 25 14:20:36 new init: Disconnected from system bus
> Oct 25 14:20:38 new rpcbind: rpcbind terminating on signal. Restart with
> "rpcbind -w"
> Oct 25 14:20:38 new auditd[2704]: The audit daemon is exiting.
> Oct 25 14:20:38 new kernel: type=1305 audit(1477430438.399:37765):
> audit_pid=0 old=2704 auid=4294967295 ses=4294967295 res=1
> Oct 25 14:20:38 new kernel: type=1305 audit(1477430438.497:37766):
> audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
> Oct 25 14:20:38 new kernel: Kernel logging (proc) stopped.
> Oct 25 14:20:38 new rsyslogd: [origin software="rsyslogd"
> swVersion="5.8.10" x-pid="2738" x-info="http://www.rsyslog.com;] exiting
> on signal 15.
>
>
> if its booted without a clean shutdown, it will do some file system
> checking and such while starting.
>
>
> --
> john r pierce, recycling bits in santa cruz
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread Eero Volotinen 
you could use smart ups and connect information from it to system, so it
can shutdown system in clean way.

Eero

2016-10-30 7:12 GMT+02:00 Hadi Motamedi :

> Dear All
> I am using a centos server for cdr billing and mediation device on a remote
> network. I am experiencing problem that I am suspicious it comes from main
> supply power cut at the remote site. The power supply to the remote site
> comes from battery charger that will be automatically switched in circuit
> under main supply power cut but cannot provide adequate power for more than
> 2 hours . I am suspicious that the remote system is suffering from many
> frequent main supply power cut . Can you please do me favor and let me know
> if there is any log on my centos server that I can check to see if there
> would be many frequent power cut there ?
> Thank you for your time
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Power Cut

2016-10-30 Thread John R Pierce 

On 10/29/2016 10:12 PM, Hadi Motamedi wrote:

I am using a centos server for cdr billing and mediation device on a remote
network. I am experiencing problem that I am suspicious it comes from main
supply power cut at the remote site. The power supply to the remote site
comes from battery charger that will be automatically switched in circuit
under main supply power cut but cannot provide adequate power for more than
2 hours . I am suspicious that the remote system is suffering from many
frequent main supply power cut . Can you please do me favor and let me know
if there is any log on my centos server that I can check to see if there
would be many frequent power cut there ?


look at /var/log/messages for reboots without shutdowns.

centos 6 linux boot starts logging something like...

Oct 25 15:01:25 new kernel: imklog 5.8.10, log source = /proc/kmsg started.
Oct 25 15:01:25 new rsyslogd: [origin software="rsyslogd" 
swVersion="5.8.10" x-pid="2740" x-info="http://www.rsyslog.com;] start

Oct 25 15:01:25 new kernel: Initializing cgroup subsys cpuset
Oct 25 15:01:25 new kernel: Initializing cgroup subsys cpu
Oct 25 15:01:25 new kernel: Linux version 2.6.32-642.6.1.el6.x86_64 
(mockbu...@worker1.bsys.centos.org) (gcc version 4.4.7 20120313 (Red Hat 
4.4.7-17) (GCC) ) #1 SMP Wed Oct 5 00:36:12 UTC 2016



followed by tons more about all the stuff starting up


when its properly shutdown, you'd see something like this after 
everything has stopped


Oct 25 14:20:36 new init: Disconnected from system bus
Oct 25 14:20:38 new rpcbind: rpcbind terminating on signal. Restart with 
"rpcbind -w"

Oct 25 14:20:38 new auditd[2704]: The audit daemon is exiting.
Oct 25 14:20:38 new kernel: type=1305 audit(1477430438.399:37765): 
audit_pid=0 old=2704 auid=4294967295 ses=4294967295 res=1
Oct 25 14:20:38 new kernel: type=1305 audit(1477430438.497:37766): 
audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1

Oct 25 14:20:38 new kernel: Kernel logging (proc) stopped.
Oct 25 14:20:38 new rsyslogd: [origin software="rsyslogd" 
swVersion="5.8.10" x-pid="2738" x-info="http://www.rsyslog.com;] exiting 
on signal 15.



if its booted without a clean shutdown, it will do some file system 
checking and such while starting.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos