Proxmox API error log / error creating VM disk

[paultjuh]

I'm using the third-party proxmox-csi plugin for Kubernetes to create VM disks. As of the new version, I can't create new disks anymore. I get a 500 internal server error from the Proxmox API. I have been looking into the logs for the csi plugin, but I think the details from the server error of the API would be very helpful. I can only find an access log though. Is there a way to enable detailed logging for the API server?

 

[Eduardo Taboada]

Hi, you can find the API HTTP access log at /var/log/pmgproxy/pmgproxy.log

 

[paultjuh]

Hi, you can find the API HTTP access log at /var/log/pmgproxy/pmgproxy.log

Hi, Thanks, but that is the Access Log, not the error/debug log. It also got moved to `/var/log/pveproxy/access.log` on the newest version.

 

[paultjuh]

I also started pvedaemon in debug modus `pvedaemon start --debug`, but I only get connection logging, no error logging

 

[Eduardo Taboada]

pvedaemon start --debug 1?

pvedaemon start [OPTIONS]
Start the daemon.
--debug <boolean> (default =0)
Debug mode - stay in foreground

 

[paultjuh]

pvedaemon start --debug 1?

pvedaemon start [OPTIONS]
Start the daemon.
--debug <boolean> (default =0)
Debug mode - stay in foreground

Unfortunately that only gives the following:

2025-12-06 11:38:54.521940 worker[149344]: PVE::APIServer::AnyEvent +1937: (eval): ACCEPT FH9 CONN1
2025-12-06 11:38:54.530285 worker[149344]: PVE::APIServer::AnyEvent +203: client_do_disconnect: close connection AnyEvent::Handle=HASH(0x566a35637ad0)
2025-12-06 11:38:54.530322 worker[149344]: PVE::APIServer::AnyEvent +178: __ANON__: CLOSE FH9
2025-12-06 11:38:54.530350 worker[149344]: PVE::APIServer::AnyEvent +203: client_do_disconnect: DISCONNECT CONN0

 

[paultjuh]

Unfortunately the same applies to starting `pve-ha-crm` and `pve-ha-lrm` in debug modus: No (useful) logging what so ever, while the server gives a 500 internal server error.

 

[Eduardo Taboada]

I dont test this solution, but you can read this post, may help you

D

Thread 'API returns 500 but no logs'

Jul 27, 2021

Hello,

I seem to have an unusual problem which happened shortly after upgrading to PVE 7.

I have an application which creates LXC containers on a PVE cluster over API. Recently, it started getting 500 status code in response to POST /api2/json/nodes/node1/lxc. The response body does not have any content, so no error message is sent. The authentication call to node1 works, but LXC creation does not.

Using the same input parameters exactly (same ID, network settings, image, limits, etc) over Web UI causes no problem, the container is created.

I doubt it is a problem with the...

• Don Daniello
• Replies: 12
• Forum: Proxmox VE: Installation and configuration

 

[paultjuh]

I dont test this solution, but you can read this post, may help you

D

Thread 'API returns 500 but no logs'

Jul 27, 2021

Hello,

I seem to have an unusual problem which happened shortly after upgrading to PVE 7.

I have an application which creates LXC containers on a PVE cluster over API. Recently, it started getting 500 status code in response to POST /api2/json/nodes/node1/lxc. The response body does not have any content, so no error message is sent. The authentication call to node1 works, but LXC creation does not.

Using the same input parameters exactly (same ID, network settings, image, limits, etc) over Web UI causes no problem, the container is created.

I doubt it is a problem with the...

• Don Daniello
• Replies: 12
• Forum: Proxmox VE: Installation and configuration

Thanks, this helped me finding the issue:

Adding the following lines to `/usr/share/perl5/PVE/API2/Storage/Content.pm` to the create function:

       use Data::Dumper;
       use Sys::Syslog;
       syslog('info', Dumper($param));

The call was missing the extension in the filename (.raw)