Off
- Thread starter Cantalupo
- Start date
Yes friend, everything is working.
I have root access via SSH.
But when I go in my browser the panel that uses port 8006 did not open.
It stopped working.
http://i.imgur.com/wurTSYA.png
I have root access via SSH.
But when I go in my browser the panel that uses port 8006 did not open.
It stopped working.
http://i.imgur.com/wurTSYA.png
All VMs work perfectly ... but the proxmox panel does not.
Code:
# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Wed 2017-01-25 02:25:15 BRT; 1 day 8h ago
Main PID: 28975 (code=exited, status=0/SUCCESS)
Jan 25 02:25:15 ns3038228 pveproxy[3331]: start failed - Unable to create new inotify object: Too many open files at /usr/share/perl...ine 389.
Jan 25 02:25:15 ns3038228 pveproxy[3331]: start failed - Unable to create new inotify object: Too many open files at /usr/share/perl...ine 389.
Jan 25 02:25:15 ns3038228 systemd[1]: pveproxy.service: control process exited, code=exited status=255
Jan 25 02:25:15 ns3038228 systemd[1]: Failed to start PVE API Proxy Server.
Jan 25 02:25:15 ns3038228 systemd[1]: Unit pveproxy.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
something on your system is consuming your inotify ressources (it is an OS ressource ) this is why a reboot was necessary
do you have other software installted on your host besides PVE who could use these ressources ? ( a backup programm ) ?
To further debug this:
what is the whole output of the error message ?
try
<code>
grep --max-count 1 'unable to create new inotify object' /var/log/*
</code>
also have a look at your current inotify instants by calling
<code>
find /proc/*/fd/* -type l -lname 'anon_inode:inotify' 2>/dev/nul | wc -l
</code>
on my system that's
33
also is your pve up to date (current version is 4.4)
do you have other software installted on your host besides PVE who could use these ressources ? ( a backup programm ) ?
To further debug this:
what is the whole output of the error message ?
try
<code>
grep --max-count 1 'unable to create new inotify object' /var/log/*
</code>
also have a look at your current inotify instants by calling
<code>
find /proc/*/fd/* -type l -lname 'anon_inode:inotify' 2>/dev/nul | wc -l
</code>
on my system that's
33
also is your pve up to date (current version is 4.4)
Is there any way to fix this?
I only have the Proxmox in the machine.
And the VPS running.
Enter the code the and presented this message:
http://i.imgur.com/dhb3iZB.png
Thanks for listening.
I only have the Proxmox in the machine.
And the VPS running.
Enter the code the and presented this message:
Code:
root@alcyone:~# grep --max-count 1 'unable to create new inotify object' /var/log/*
grep: /var/log/apt: Is a directory
grep: /var/log/corosync: Is a directory
grep: /var/log/fsck: Is a directory
grep: /var/log/glusterfs: Is a directory
grep: /var/log/installer: Is a directory
grep: /var/log/lxc: Is a directory
grep: /var/log/pve: Is a directory
grep: /var/log/pveproxy: Is a directory
root@alcyone:~#
Code:
root@alcyone:~# find /proc/*/fd/* -type l -lname 'anon_inode:inotify' 2>/dev/nul | wc -l
0
root@alcyone:~#
Code:
root@alcyone:~# free
total used free shared buffers cached
Mem: 32844172 32492220 351952 1369444 2184908 20876112
-/+ buffers/cache: 9431200 23412972
Swap: 32765944 600420 32165524
root@alcyone:~#Thanks for listening.
https://bugzilla.proxmox.com/show_bug.cgi?id=1042
finding out why you are running out might still be advisable
finding out why you are running out might still be advisable
Hello, guys I made the change in the file and it really worked.
But it does not take long and falls again.
I have very useful information ...
I noticed that when proxmox port 8006 crashes, i receive an error message via email:
But it does not take long and falls again.
I have very useful information ...
I noticed that when proxmox port 8006 crashes, i receive an error message via email:
- Subject: Cron <root@server> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
Code:
/etc/cron.daily/logrotate:
Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and 'journalctl -xn' for details.
Job for spiceproxy.service failed. See 'systemctl status spiceproxy.service' and 'journalctl -xn' for details.
error: error running shared postrotate script for '/var/log/pveproxy/access.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1