Recent content by lodperera

Well just closing this thread. It seems that the node ran out of memory so it crashed. Nothing to do with physical drives even though they showed some errors. Thank you @udo @jeffwadsworth for replying and taking your time.

That did the trick. I added the locale setting on my centos container as follows. # cat /etc/locale.conf LANG=en_US.utf8 Then rebooted, it was all good. Thanks.

I tried the following 1. Using crontab to run this command at reboot @reboot export LANG=en_US.UTF-8 It didn't seem to work. 2. Then I tried to add it to the boot time script /etc/rc.d/rc.local export LANG=en_US.UTF-8 It didn't work as well. I had to manually run the command both times.

I'm running CentOS 7 LXC container on proxmox 5.1 Issue is that the LANG= changes to empty after reboot. I have to run export LANG=en_US.UTF-8 to change it back after the reboot. Is there a way to persistently set this up for LXC? proxmox-ve: 5.1-36 (running kernel: 4.13.13-5-pve)...

The errors seems to be increasing but I still do not understand why it rebooted the whole node and send the cluster to a zombie state. root@s1n1:/var/log# smartctl --scan-open /dev/sda -d scsi # /dev/sda, SCSI device /dev/sdb -d scsi # /dev/sdb, SCSI device /dev/sdc -d scsi # /dev/sdc, SCSI...

Hi Udo, Thank you for that. Attached. Hard disk smart on node 1 and 2 RAID Adapter info on node 1 and 2 PS : I can see some errors on node 2 hard disk smart not sure what to do.

Hi J, I do not have smarts due to the RAID card I use I believe. root@s1n2:/var/log# smartctl -a /dev/sda smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.4.35-1-pve] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION ===...

Thank you for getting back to me. Now it's all good. For record I didn't update proxmox nodes. My backup server synology started doing it's automated update and restarted itself while the VM backup was happening. I'm going to list some codes I ran to bring a corrupted OSD up so the nubes like...

Update: I found out that our backup server started updating itself at the same time the VM backup was happening and backup server restarted itself. Since proxmox couldn't send the backup it went all suicide it seems. This happened at around 1.40 am OCT 7. I have attached logs for someone who...

OK so I'm just writing stuff what happened. I stopped all nodes and rebooted one by one I did noout via GUI then I had to manually start OSDs However 6 out of 12 didn't like to start I removed OSD and put them back using GUI 2 disks didn't want to put in as OSDs Those two disks were giving...

I got access to gui. used another browser could be cache related. Still having issues with ceph I'm guessing I might have to remove and re-add them

Hi Guys, I'm on panic mode, any help is appreciated. have 4 nodes in production root@s2n1:~# pveversion -v proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve) pve-manager: 4.4-2 (running version: 4.4-2/80259e05) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.4.13-1-pve: 4.4.13-56...

I had to add the IP address of the server into IPSET using the name ipfilter-net0 http://pve.proxmox.com/wiki/Firewall#pve_firewall_ip_sets

I did some further testing. I added icmp accept out and in. still it didn't do any change. It is because it has DROP all rule to begin with. Can any one please be kind enough to explain whether this behavior is expected? root@s1n2:~# iptables -L tap103i0-OUT -v Chain tap103i0-OUT (1...

Hi Buddy, Hope you could have a quick look at the weird issue I'm having with firewall. https://forum.proxmox.com/threads/unable-to-ping-outside-when-firewall-turned-on.32883/ It might be a quick config change that I'm overlooking. thank you for your time. re LOD