Hello,
I want to setup a SuSe manager 3.0 test installation.
After the database settings, I have to enter my SCC credentials to connect to the customer center.
The test isn’t successfull:
[QUOTE]Cannot download list of repositories.
Reason: Response code 401
Test result: failure[/QUOTE]
With the entered credentials, I can login the scc via browser: https://scc.suse.com/login
I’m using a proxy. Could this be the cause of the problem?
BR
Christian
[QUOTE=christianmolecki;32674]Hello,
I want to setup a SuSe manager 3.0 test installation.
After the database settings, I have to enter my SCC credentials to connect to the customer center.
The test isn’t successfull:
With the entered credentials, I can login the scc via browser: https://scc.suse.com/login
I’m using a proxy. Could this be the cause of the problem?
BR
Christian[/QUOTE]
At this step you should use your organization password not the password you use to login to scc.
Thomas
[QUOTE=thsundel;32677]At this step you should use your organization password not the password you use to login to scc.
Thomas[/QUOTE]
It’s not so easy to find, so let me guide you… Login to scc in a browser, click Organization at the top, then Organization credentials, there you will find the username and password you should use.
Thomas
thk you Thomas, I found the organisation credentials.
Unfortunately the Tomcat won’t start and there is an empty Tomcat logfile directory.
[QUOTE=christianmolecki;32679]thk you Thomas, I found the organisation credentials.
Unfortunately the Tomcat won’t start and there is an empty Tomcat logfile directory.[/QUOTE]
So no errors during install, have you checked: /var/log/susemanager_setup.*
Thomas
STDERR:
[QUOTE]Failed to stop salt-api.service: Unit salt-api.service not loaded.
atftpd.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig atftpd on
ERROR: spacewalk-setup failed
[/QUOTE]
STDOUT:
[QUOTE]/var/spacewalk already exists. Leaving it untouched.
Open needed firewall ports…
Performing forced re-installation!
Shutting down spacewalk services…
Done.
Delete existing database…
Delete existing salt minion keys
CREATE ROLE
- Loading answer file: /root/spacewalk-answers.
** Database: Setting up database connection for PostgreSQL backend.
** Database: Populating database.
** Database: --clear-db option used. Clearing database.
** Database: Shutting down spacewalk services that may be using DB.
** Database: Services stopped. Clearing DB.
*** Progress: #
- Configuring tomcat.
- Setting up users and groups.
** GPG: Initializing GPG and importing key.
- Performing initial configuration.
- Configuring apache SSL virtual host.
- Configuring jabberd.
- Creating SSL certificates.
** SSL: Generating CA certificate.
** SSL: Deploying CA certificate.
** SSL: Generating server certificate.
** SSL: Storing SSL certificates.
- Deploying configuration files.
- Update configuration in database.
- Setting up Cobbler…
- Restarting services.
Tomcat failed to start properly or the installer ran out of tries. Please check /var/log/tomcat*/catalina.out for errors.
[/QUOTE]
[QUOTE=christianmolecki;32681]STDERR:
STDOUT:[/QUOTE]
Hmm… Looks almost like my logs but I don’t have “Failed to stop salt-api.service: Unit salt-api.service not loaded.” nor “Tomcat failed to start properly or the installer ran out of tries. Please check /var/log/tomcat*/catalina.out for errors.”.
How did you install SUMA, I did it with this command: zypper in -t pattern suma_server and how much RAM does this host have?
Thomas
I installed SUMA via YAST2->AddOns.
The error … salt-api.service could caused by a setup over an existing configuration.
The virtual maschine has 8 GB RAM.