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

VCenter 7 Connect stucks at Sending Login request #308

Closed
krappi01 opened this issue Dec 23, 2021 · 8 comments
Closed

VCenter 7 Connect stucks at Sending Login request #308

krappi01 opened this issue Dec 23, 2021 · 8 comments
Labels

Comments

@krappi01
Copy link

Expected Behavior

Module should connect to VCenter and import all the stuff

Current Behavior

No data is loaded from VCenter and icingacli vspheredb daemon run --debug --trace shows as last entry:
debug: [api stsddf-vcenter01.example.com (id=5)] Sending Login request to https://stsddf-vcenter01.example.com/sdk
In a browser the /sdk endpoint from VCenter answers with HTTP 404 not found, other endpoints like /sdk/vimService.wsdl work.
It seems that the url is incomplete.

When connecting directly to ESX host, it works, but /icingaweb2/vspheredb/configuration/servers shows the following error message:
Got no connection information. Is the Damon running?
The exception message from ConfigurationController.php:106 is:
Promise rejected with unexpected value of type TypeError

Your Environment

  • VMware vCenter®/ESXi™-Version: 7.0.3 Build 18901211
  • Version/GIT-Hash of this module: 1.2.1
  • Icinga Web 2 version: 2.9.5
  • Operating System and version: CentOS 8
  • Webserver, PHP versions: 8.0.14
@Thomas-Gelf
Copy link
Contributor

Please stop the daemon...

systemctl stop icinga-vspheredb.service

...switch to it's user...

su - icingavspheredb -s /bin/bash

...and start the daemon with debug level in the foreground:

icingacli vspheredb daemon run --debug

Please share the (anonymized) output.

@Thomas-Gelf
Copy link
Contributor

NB: 404 for /sdk is fine. Your browser doesn't send a valid SOAP request, and that's why the VCenter gives you a 404

@krappi01
Copy link
Author

Hi, here is the output:

_PHP Fatal error: Uncaught Error: Call to a member function translate() on null in /usr/share/php/Icinga/Application/functions.php:35
Stack trace:
#0 /usr/share/php/Icinga/Application/Config.php(328): t()
#1 /usr/share/php/Icinga/Application/Config.php(397): Icinga\Application\Config::fromIni()
#2 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(589): Icinga\Application\Config::app()
#3 /usr/share/php/Icinga/Application/Cli.php(42): Icinga\Application\ApplicationBootstrap->loadConfig()
#4 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(416): Icinga\Application\Cli->bootstrap()
#5 /usr/bin/icingacli(7): Icinga\Application\ApplicationBootstrap::start()
#6 {main}
thrown in /usr/share/php/Icinga/Application/functions.php on line 35

Fatal error: Uncaught Error: Call to a member function translate() on null in /usr/share/php/Icinga/Application/functions.php:35
Stack trace:
#0 /usr/share/php/Icinga/Application/Config.php(328): t()
#1 /usr/share/php/Icinga/Application/Config.php(397): Icinga\Application\Config::fromIni()
#2 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(589): Icinga\Application\Config::app()
#3 /usr/share/php/Icinga/Application/Cli.php(42): Icinga\Application\ApplicationBootstrap->loadConfig()
#4 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(416): Icinga\Application\Cli->bootstrap()
#5 /usr/bin/icingacli(7): Icinga\Application\ApplicationBootstrap::start()
#6 {main}
thrown in /usr/share/php/Icinga/Application/functions.php on line 35_

Are we missing a PHP module?

@krappi01
Copy link
Author

Oh, it was a permission issue.
Changing the permissions solved it:
chown -R apache:icingaweb2 /etc/icingaweb2/
Thanks!

@krappi01 krappi01 reopened this Dec 23, 2021
@krappi01
Copy link
Author

The PHP error messages are away now, but it still stucks at:
Sending Login request to...

@Thomas-Gelf
Copy link
Contributor

Please show the FULL (anonymized) log output. In addition please share your Incubator module version and double-check your credentials.

@krappi01
Copy link
Author

When using the administrator@vsphere.local credentials instead of root everything works fine.
Thanks!

@Thomas-Gelf
Copy link
Contributor

You're welcome!

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

No branches or pull requests

2 participants