Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

change mgt ip

Pages: 1 2

Hi, is it possible with a running Petasan to change the management gui ip ?

greetings marcel

Hi, can i cange it in /etc/network/interfaces ?

greetings marcel

Hi

 

on each node customize these 3 configs  ?

systemctl stop petasan-file-sync

/etc/hosts
/opt/petasan/config/cluster_info.json
/opt/petasan/config/node_info.json

systemctl start petasan-file-sync

 

greetings marcel

you do not need to modify cluster_info.json unless you are changing interface or bonds which applies to all nodes, but just changing the ip of a node it is not needed.

You will however need to change the node_info.json local file (as you showed), as well as in consul, as below example to change a node NODE01

consul kv get PetaSAN/Nodes/NODE01 > x
nano x # edit management ip
consul kv put PetaSAN/Nodes/NODE01 @x

hi i have edit the
/opt/petasan/config/node_info.json
adapted and also
consul kv get PetaSAN / Nodes / NODE01> x
nano x # edit management ip
consul kv put PetaSAN / Nodes / NODE01 @x

but the webgui time after the login
"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. "

what did i do wrong? :(

MfG marcel

did you also edit /etc/network/interfaces

can you ssh using the new ip ?

hi yes I have also adjusted
/etc/network/interfaces

ip addresses match but the webui is no longer available after i entered the login data this error appears

 

i have edit also the /etc/hosts

and /etc/nginx/sites-enabled/petasan_admin

 

root@Storage-3:/etc/nginx/sites-enabled# sudo nginx
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:5000 failed (98: Address already in use)
nginx: [emerg] still could not bind()
root@Storage-3:/etc/nginx/sites-enabled#

 

 

best regards

marcel

root@Storage-3:/etc/nginx/sites-enabled# systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2021-04-26 10:03:48 CEST; 21s ago
Docs: man:nginx(8)
Process: 249035 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS)
Process: 249037 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 249036 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Main PID: 249038 (nginx)
Tasks: 25 (limit: 4915)
CGroup: /system.slice/nginx.service
├─249038 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
├─249039 nginx: worker process
├─249040 nginx: worker process
├─249041 nginx: worker process
├─249042 nginx: worker process
├─249043 nginx: worker process
├─249044 nginx: worker process
├─249045 nginx: worker process
├─249046 nginx: worker process
├─249047 nginx: worker process
├─249048 nginx: worker process
├─249049 nginx: worker process
├─249050 nginx: worker process
├─249051 nginx: worker process
├─249052 nginx: worker process
├─249053 nginx: worker process
├─249054 nginx: worker process
├─249055 nginx: worker process
├─249056 nginx: worker process
├─249057 nginx: worker process
├─249058 nginx: worker process
├─249059 nginx: worker process
├─249060 nginx: worker process
├─249061 nginx: worker process
└─249062 nginx: worker process

Apr 26 10:03:48 Storage-3 systemd[1]: Starting A high performance web server and a reverse proxy server...
Apr 26 10:03:48 Storage-3 systemd[1]: Started A high performance web server and a reverse proxy server.
root@Storage-3:/etc/nginx/sites-enabled#

Hi any news for me ?

 

best regards

marcel

Apologies i did not see this..

i see you have address already in use errors..did you reboot the node after changing ips and still get this error..or you want to avoid reboots ?

can you ssh using the new ip ? is everything running ok apart from web ui ?

you only changed the management ip correct or did you also change backend ip ?

Pages: 1 2