Not login
Pages: 1 2
iPrime
1 Post
October 19, 2016, 11:36 amQuote from iPrime on October 19, 2016, 11:36 amCan't login to dashboard (admin / cluster password not work). How to reset password?
Can't login to dashboard (admin / cluster password not work). How to reset password?
admin
2,918 Posts
October 19, 2016, 2:00 pmQuote from admin on October 19, 2016, 2:00 pmThe initial management ui password for user "admin" is simply "password" and not the cluster password
you can change it once logged in.
the cluster password is the linux os root password, which you can use for ssh to administer the node at the os level. it is different than the web ui password
Apologies this was an error in the documentation and will be corrected
The initial management ui password for user "admin" is simply "password" and not the cluster password
you can change it once logged in.
the cluster password is the linux os root password, which you can use for ssh to administer the node at the os level. it is different than the web ui password
Apologies this was an error in the documentation and will be corrected
dan
5 Posts
February 17, 2017, 2:38 pmQuote from dan on February 17, 2017, 2:38 pmIs there a default ssh / user password? I am installing on baremetal, with the latest release, but the servers are not pinging or responding to http://xxx.xxx.xxx:5001.
I'd like to login locally and troubleshoot.
Is there a default ssh / user password? I am installing on baremetal, with the latest release, but the servers are not pinging or responding to http://xxx.xxx.xxx:5001.
I'd like to login locally and troubleshoot.
Last edited on February 17, 2017, 2:40 pm · #3
admin
2,918 Posts
February 17, 2017, 3:23 pmQuote from admin on February 17, 2017, 3:23 pmNo there is no default password. It is set when you create the cluster during deployment.
After using the installer and reboot. can you ping on the management interface assigned during install from the location of your browser
?
Does the node console, the blue screen displayed when you connect a display monitor to the node, show the correct ip/interface settings ?
Can you try re-installing ? If things do not work, i can send you a version with a default password to debug the issue : send me your mail on:
admin @ petasan.org
and i will give you a link. to download
No there is no default password. It is set when you create the cluster during deployment.
After using the installer and reboot. can you ping on the management interface assigned during install from the location of your browser
?
Does the node console, the blue screen displayed when you connect a display monitor to the node, show the correct ip/interface settings ?
Can you try re-installing ? If things do not work, i can send you a version with a default password to debug the issue : send me your mail on:
admin @ petasan.org
and i will give you a link. to download
slacker87
12 Posts
March 29, 2017, 3:20 pmQuote from slacker87 on March 29, 2017, 3:20 pm**Bump** As I'm having the exact same issue.
Install completes with no errors, but upon rebooting I'm stuck at the ubuntu login prompt screen and nothing pings back.
**Bump** As I'm having the exact same issue.
Install completes with no errors, but upon rebooting I'm stuck at the ubuntu login prompt screen and nothing pings back.
slacker87
12 Posts
March 29, 2017, 7:18 pmQuote from slacker87 on March 29, 2017, 7:18 pmI managed to hop into the web interface and set things up after messing around with ports a few times, but I still only ever see the ubuntu login prompt on boot, no nice splash page of ip information.
I managed to hop into the web interface and set things up after messing around with ports a few times, but I still only ever see the ubuntu login prompt on boot, no nice splash page of ip information.
admin
2,918 Posts
March 29, 2017, 8:12 pmQuote from admin on March 29, 2017, 8:12 pmSo were you able to access the web deployment interface ? did you deploy 3 nodes and build the cluster ? The blue console screen not showing is strange, if you found you had mis-configured ports and fixed it, i recommend you re-install.
So were you able to access the web deployment interface ? did you deploy 3 nodes and build the cluster ? The blue console screen not showing is strange, if you found you had mis-configured ports and fixed it, i recommend you re-install.
slacker87
12 Posts
March 29, 2017, 8:46 pmQuote from slacker87 on March 29, 2017, 8:46 pmI did a reinstall but still no blue splash on boot. I also did manage to get a 3 node cluster up through just the web management pages.
I did a reinstall but still no blue splash on boot. I also did manage to get a 3 node cluster up through just the web management pages.
admin
2,918 Posts
March 30, 2017, 6:34 amQuote from admin on March 30, 2017, 6:34 amHi again,
Well it is good the cluster was built. But i am not clear why the console does not appear. Is this the only issue you see. Is everything else working fine ? Can you create disks ? is the system responsive / fast ?
If you are familiar with linux, can you log into any of the nodes (that have the console issue ) using ssh and provide root as user and the cluster password as the login password and tell me the output of:
ps aux | grep console
cat /etc/network/interfaces
Hi again,
Well it is good the cluster was built. But i am not clear why the console does not appear. Is this the only issue you see. Is everything else working fine ? Can you create disks ? is the system responsive / fast ?
If you are familiar with linux, can you log into any of the nodes (that have the console issue ) using ssh and provide root as user and the cluster password as the login password and tell me the output of:
ps aux | grep console
cat /etc/network/interfaces
ally2030
2 Posts
April 6, 2017, 2:47 pmQuote from ally2030 on April 6, 2017, 2:47 pmsometimes console.sh not work as expected:
"systemctl stop getty@tty2.service" never got stopped.
afer login, manually run "systemctl stop getty@tty2.service",
then petasan-console replace getty@tty2.
to complete disable getty@tty2:
sed -i 's/getty@tty2.service //g' /lib/systemd/system/getty.target.wants/getty-static.service
sometimes console.sh not work as expected:
"systemctl stop getty@tty2.service" never got stopped.
afer login, manually run "systemctl stop getty@tty2.service",
then petasan-console replace getty@tty2.
to complete disable getty@tty2:
sed -i 's/getty@tty2.service //g' /lib/systemd/system/getty.target.wants/getty-static.service
Pages: 1 2
Not login
iPrime
1 Post
Quote from iPrime on October 19, 2016, 11:36 amCan't login to dashboard (admin / cluster password not work). How to reset password?
Can't login to dashboard (admin / cluster password not work). How to reset password?
admin
2,918 Posts
Quote from admin on October 19, 2016, 2:00 pmThe initial management ui password for user "admin" is simply "password" and not the cluster password
you can change it once logged in.
the cluster password is the linux os root password, which you can use for ssh to administer the node at the os level. it is different than the web ui password
Apologies this was an error in the documentation and will be corrected
The initial management ui password for user "admin" is simply "password" and not the cluster password
you can change it once logged in.
the cluster password is the linux os root password, which you can use for ssh to administer the node at the os level. it is different than the web ui password
Apologies this was an error in the documentation and will be corrected
dan
5 Posts
Quote from dan on February 17, 2017, 2:38 pmIs there a default ssh / user password? I am installing on baremetal, with the latest release, but the servers are not pinging or responding to http://xxx.xxx.xxx:5001.
I'd like to login locally and troubleshoot.
Is there a default ssh / user password? I am installing on baremetal, with the latest release, but the servers are not pinging or responding to http://xxx.xxx.xxx:5001.
I'd like to login locally and troubleshoot.
admin
2,918 Posts
Quote from admin on February 17, 2017, 3:23 pmNo there is no default password. It is set when you create the cluster during deployment.
After using the installer and reboot. can you ping on the management interface assigned during install from the location of your browser
?
Does the node console, the blue screen displayed when you connect a display monitor to the node, show the correct ip/interface settings ?
Can you try re-installing ? If things do not work, i can send you a version with a default password to debug the issue : send me your mail on:
admin @ petasan.org
and i will give you a link. to download
No there is no default password. It is set when you create the cluster during deployment.
After using the installer and reboot. can you ping on the management interface assigned during install from the location of your browser
?
Does the node console, the blue screen displayed when you connect a display monitor to the node, show the correct ip/interface settings ?
Can you try re-installing ? If things do not work, i can send you a version with a default password to debug the issue : send me your mail on:
admin @ petasan.org
and i will give you a link. to download
slacker87
12 Posts
Quote from slacker87 on March 29, 2017, 3:20 pm**Bump** As I'm having the exact same issue.
Install completes with no errors, but upon rebooting I'm stuck at the ubuntu login prompt screen and nothing pings back.
**Bump** As I'm having the exact same issue.
Install completes with no errors, but upon rebooting I'm stuck at the ubuntu login prompt screen and nothing pings back.
slacker87
12 Posts
Quote from slacker87 on March 29, 2017, 7:18 pmI managed to hop into the web interface and set things up after messing around with ports a few times, but I still only ever see the ubuntu login prompt on boot, no nice splash page of ip information.
I managed to hop into the web interface and set things up after messing around with ports a few times, but I still only ever see the ubuntu login prompt on boot, no nice splash page of ip information.
admin
2,918 Posts
Quote from admin on March 29, 2017, 8:12 pmSo were you able to access the web deployment interface ? did you deploy 3 nodes and build the cluster ? The blue console screen not showing is strange, if you found you had mis-configured ports and fixed it, i recommend you re-install.
So were you able to access the web deployment interface ? did you deploy 3 nodes and build the cluster ? The blue console screen not showing is strange, if you found you had mis-configured ports and fixed it, i recommend you re-install.
slacker87
12 Posts
Quote from slacker87 on March 29, 2017, 8:46 pmI did a reinstall but still no blue splash on boot. I also did manage to get a 3 node cluster up through just the web management pages.
I did a reinstall but still no blue splash on boot. I also did manage to get a 3 node cluster up through just the web management pages.
admin
2,918 Posts
Quote from admin on March 30, 2017, 6:34 amHi again,
Well it is good the cluster was built. But i am not clear why the console does not appear. Is this the only issue you see. Is everything else working fine ? Can you create disks ? is the system responsive / fast ?
If you are familiar with linux, can you log into any of the nodes (that have the console issue ) using ssh and provide root as user and the cluster password as the login password and tell me the output of:
ps aux | grep console
cat /etc/network/interfaces
Hi again,
Well it is good the cluster was built. But i am not clear why the console does not appear. Is this the only issue you see. Is everything else working fine ? Can you create disks ? is the system responsive / fast ?
If you are familiar with linux, can you log into any of the nodes (that have the console issue ) using ssh and provide root as user and the cluster password as the login password and tell me the output of:
ps aux | grep console
cat /etc/network/interfaces
ally2030
2 Posts
Quote from ally2030 on April 6, 2017, 2:47 pmsometimes console.sh not work as expected:
"systemctl stop getty@tty2.service" never got stopped.
afer login, manually run "systemctl stop getty@tty2.service",
then petasan-console replace getty@tty2.
to complete disable getty@tty2:
sed -i 's/getty@tty2.service //g' /lib/systemd/system/getty.target.wants/getty-static.service
sometimes console.sh not work as expected:
"systemctl stop getty@tty2.service" never got stopped.
afer login, manually run "systemctl stop getty@tty2.service",
then petasan-console replace getty@tty2.
to complete disable getty@tty2:
sed -i 's/getty@tty2.service //g' /lib/systemd/system/getty.target.wants/getty-static.service