Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 Internal Server Error type object argument after ** must be a mapping, not NoneType #25

Closed
jaydwit opened this issue May 2, 2020 · 5 comments

Comments

@jaydwit
Copy link

jaydwit commented May 2, 2020

Hi-
Trying to get this up and running and keep running into a 500 error I cannot seem to figure out.

Running the exporter on a proxmox node and prometheus remote.

journal on proxmox shows a failed get request.
"GET /pve?module=default HTTP/1.1" 500 -

UI and a curl shows this error-

`

<title>500 Internal Server Error</title>

Internal Server Error

type object argument after ** must be a mapping, not NoneType

`

I cannot for the life of me figure this out so any help would be great! Let me know what you need and I'll get it for you.

Used this guide here to get it installed if that helps any.
https://blog.zwindler.fr/2020/01/06/proxmox-ve-prometheus/?unapproved=21086&moderation-hash=07cf6a6aa2cbec783032cc651e69b38a#comment-21086

@jaydwit jaydwit changed the title 500 Internal Server Error 500 Internal Server Error type object argument after ** must be a mapping, not NoneType May 2, 2020
@znerol
Copy link
Member

znerol commented May 2, 2020

You are absolutely right, the error message is not helpful at all. Luckily the ** operator is only used twice, and the most likely problem is that config is None in collect_pve.

The module url parameter maps to toplevel keys in the config file. Thus make sure you have the default toplevel key in your YAML configuration file.

HTH

@znerol
Copy link
Member

znerol commented May 2, 2020

Opened #25 and #26 to avoid problems like this in the future.

@znerol
Copy link
Member

znerol commented May 3, 2020

Released version 1.2.1 with error handling and config validation improvements. Please open a new issue if problems persist.

@znerol znerol closed this as completed May 3, 2020
@jaydwit
Copy link
Author

jaydwit commented May 3, 2020

Appreciate the quick response! I'll give this a go tomorrow when I have a few minutes. Thanks again!

@jaydwit
Copy link
Author

jaydwit commented May 4, 2020

error handling helped greatly. the service is now up and running and working beautifully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants