Internal Server Error
Pages: 1 2
BILDr
16 Posts
April 8, 2020, 9:40 pmQuote from BILDr on April 8, 2020, 9:40 pmI am installing a fresh install of 2.5 on DL380 G8 hardware. There are 12 x LFF SAS and 1 x SATA O/S disk.
All three install just fine, and I can connect to them all via :5001
All of them when selecting any menu option give:
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Has anyone got any idea what this is? I am remote now and don't have physical access to the machines.
I am installing a fresh install of 2.5 on DL380 G8 hardware. There are 12 x LFF SAS and 1 x SATA O/S disk.
All three install just fine, and I can connect to them all via :5001
All of them when selecting any menu option give:
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Has anyone got any idea what this is? I am remote now and don't have physical access to the machines.
BILDr
16 Posts
April 8, 2020, 9:52 pmQuote from BILDr on April 8, 2020, 9:52 pmIt looks like I can get there by SSH. I have tried admin/password, root/password and admin/root with the password used when setting up initially and can't get in. Am I using the right credentials?
If I can get in I can get at the logs.
It looks like I can get there by SSH. I have tried admin/password, root/password and admin/root with the password used when setting up initially and can't get in. Am I using the right credentials?
If I can get in I can get at the logs.
admin
2,930 Posts
April 8, 2020, 11:46 pmQuote from admin on April 8, 2020, 11:46 pmi assume you built the clustered via deployment wizard on all nodes and that built fine, but you cannot log to the management ui on https port 443.
have you downloaded the https certificate ? if not, you can get in from port 5000, install it in your browser as trusted root authority. then log to https.
if you already passed this, i would check your network settings and connections, maybe try to re-install one more time and if still you have a problem we can look in more detail.
i assume you built the clustered via deployment wizard on all nodes and that built fine, but you cannot log to the management ui on https port 443.
have you downloaded the https certificate ? if not, you can get in from port 5000, install it in your browser as trusted root authority. then log to https.
if you already passed this, i would check your network settings and connections, maybe try to re-install one more time and if still you have a problem we can look in more detail.
BILDr
16 Posts
April 9, 2020, 7:42 amQuote from BILDr on April 9, 2020, 7:42 amI haven't got as far as past the deployment wizard.
This is a fresh build from USB stick. That process works fine, I can assign an IP address, password, select network card etc (all nodes eth0 - same card). I restart the nodes and then connect to them to deploy and whatever of the three options I select I get this message.
I am unable to get past this point but can still connect to each new server (I guess it's not a node yet) on port :5001
I haven't got as far as past the deployment wizard.
This is a fresh build from USB stick. That process works fine, I can assign an IP address, password, select network card etc (all nodes eth0 - same card). I restart the nodes and then connect to them to deploy and whatever of the three options I select I get this message.
I am unable to get past this point but can still connect to each new server (I guess it's not a node yet) on port :5001
admin
2,930 Posts
April 9, 2020, 8:39 amQuote from admin on April 9, 2020, 8:39 amSo after you install from iso and connect the deploy the node on port 5001: it gives you the error right away or do you see the message "Create New Cluster", "Join Existing Cluster" and it fails after you make your choice ?
So after you install from iso and connect the deploy the node on port 5001: it gives you the error right away or do you see the message "Create New Cluster", "Join Existing Cluster" and it fails after you make your choice ?
BILDr
16 Posts
April 9, 2020, 8:40 amQuote from BILDr on April 9, 2020, 8:40 amYes, correct! To be clear, I get the three options. I select to create a new cluster (or the same result with any option) and get this message.
Yes, correct! To be clear, I get the three options. I select to create a new cluster (or the same result with any option) and get this message.
Last edited on April 9, 2020, 9:12 am by BILDr · #6
admin
2,930 Posts
April 9, 2020, 5:21 pmQuote from admin on April 9, 2020, 5:21 pmhard to say..do you see any errors in dmesg, syslog, PetaSAN.log when you click on the ui ?
hard to say..do you see any errors in dmesg, syslog, PetaSAN.log when you click on the ui ?
Last edited on April 9, 2020, 5:22 pm by admin · #7
BILDr
16 Posts
April 9, 2020, 5:48 pmQuote from BILDr on April 9, 2020, 5:48 pmWhat are the credentials to use to access via SSH at this stage?
What are the credentials to use to access via SSH at this stage?
admin
2,930 Posts
April 9, 2020, 9:35 pmQuote from admin on April 9, 2020, 9:35 pmAt this stage of pre-deploy, there will be a menu on the blue node console, to allow a shell. this will allow you root access. type passwd to set root password, then you can ssh with that password
At this stage of pre-deploy, there will be a menu on the blue node console, to allow a shell. this will allow you root access. type passwd to set root password, then you can ssh with that password
BILDr
16 Posts
April 10, 2020, 7:17 amQuote from BILDr on April 10, 2020, 7:17 amGreat. It will be a few weeks before I have physical access to the servers once more.
Great. It will be a few weeks before I have physical access to the servers once more.
Pages: 1 2
Internal Server Error
BILDr
16 Posts
Quote from BILDr on April 8, 2020, 9:40 pmI am installing a fresh install of 2.5 on DL380 G8 hardware. There are 12 x LFF SAS and 1 x SATA O/S disk.
All three install just fine, and I can connect to them all via :5001
All of them when selecting any menu option give:
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Has anyone got any idea what this is? I am remote now and don't have physical access to the machines.
I am installing a fresh install of 2.5 on DL380 G8 hardware. There are 12 x LFF SAS and 1 x SATA O/S disk.
All three install just fine, and I can connect to them all via :5001
All of them when selecting any menu option give:
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Has anyone got any idea what this is? I am remote now and don't have physical access to the machines.
BILDr
16 Posts
Quote from BILDr on April 8, 2020, 9:52 pmIt looks like I can get there by SSH. I have tried admin/password, root/password and admin/root with the password used when setting up initially and can't get in. Am I using the right credentials?
If I can get in I can get at the logs.
It looks like I can get there by SSH. I have tried admin/password, root/password and admin/root with the password used when setting up initially and can't get in. Am I using the right credentials?
If I can get in I can get at the logs.
admin
2,930 Posts
Quote from admin on April 8, 2020, 11:46 pmi assume you built the clustered via deployment wizard on all nodes and that built fine, but you cannot log to the management ui on https port 443.
have you downloaded the https certificate ? if not, you can get in from port 5000, install it in your browser as trusted root authority. then log to https.
if you already passed this, i would check your network settings and connections, maybe try to re-install one more time and if still you have a problem we can look in more detail.
i assume you built the clustered via deployment wizard on all nodes and that built fine, but you cannot log to the management ui on https port 443.
have you downloaded the https certificate ? if not, you can get in from port 5000, install it in your browser as trusted root authority. then log to https.
if you already passed this, i would check your network settings and connections, maybe try to re-install one more time and if still you have a problem we can look in more detail.
BILDr
16 Posts
Quote from BILDr on April 9, 2020, 7:42 amI haven't got as far as past the deployment wizard.
This is a fresh build from USB stick. That process works fine, I can assign an IP address, password, select network card etc (all nodes eth0 - same card). I restart the nodes and then connect to them to deploy and whatever of the three options I select I get this message.
I am unable to get past this point but can still connect to each new server (I guess it's not a node yet) on port :5001
I haven't got as far as past the deployment wizard.
This is a fresh build from USB stick. That process works fine, I can assign an IP address, password, select network card etc (all nodes eth0 - same card). I restart the nodes and then connect to them to deploy and whatever of the three options I select I get this message.
I am unable to get past this point but can still connect to each new server (I guess it's not a node yet) on port :5001
admin
2,930 Posts
Quote from admin on April 9, 2020, 8:39 amSo after you install from iso and connect the deploy the node on port 5001: it gives you the error right away or do you see the message "Create New Cluster", "Join Existing Cluster" and it fails after you make your choice ?
So after you install from iso and connect the deploy the node on port 5001: it gives you the error right away or do you see the message "Create New Cluster", "Join Existing Cluster" and it fails after you make your choice ?
BILDr
16 Posts
Quote from BILDr on April 9, 2020, 8:40 amYes, correct! To be clear, I get the three options. I select to create a new cluster (or the same result with any option) and get this message.
Yes, correct! To be clear, I get the three options. I select to create a new cluster (or the same result with any option) and get this message.
admin
2,930 Posts
Quote from admin on April 9, 2020, 5:21 pmhard to say..do you see any errors in dmesg, syslog, PetaSAN.log when you click on the ui ?
hard to say..do you see any errors in dmesg, syslog, PetaSAN.log when you click on the ui ?
BILDr
16 Posts
Quote from BILDr on April 9, 2020, 5:48 pmWhat are the credentials to use to access via SSH at this stage?
What are the credentials to use to access via SSH at this stage?
admin
2,930 Posts
Quote from admin on April 9, 2020, 9:35 pmAt this stage of pre-deploy, there will be a menu on the blue node console, to allow a shell. this will allow you root access. type passwd to set root password, then you can ssh with that password
At this stage of pre-deploy, there will be a menu on the blue node console, to allow a shell. this will allow you root access. type passwd to set root password, then you can ssh with that password
BILDr
16 Posts
Quote from BILDr on April 10, 2020, 7:17 amGreat. It will be a few weeks before I have physical access to the servers once more.
Great. It will be a few weeks before I have physical access to the servers once more.