11-01-2020 09:20 PM - edited 07-05-2021 12:43 PM
Hi Experts,
im having issue adding MSE to prime with below error:
No response from server. it may be unreachable, or server is down or https connection to server failed.
but the mse was already added before. mse is version 8 and prime is 3.6. saw this below bug. but tried the work around and didnt help.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy43823/?rfs=iqvred
any other workaround for this issue?thanks
tia
chris
11-02-2020 12:14 AM
Check exact and or full MSE-version , seems you need 8.0.150.x
M.
11-02-2020 12:25 AM
yes thats the version i just put version 8. and as i mentioned the mse was added before. i removed it for some troubleshooting. but ended up having more troubleshooting needs to be done
11-02-2020 02:32 AM
- Try to reboot the Prime server completely , if that doesn't help either , then become root on Prime and issue the command # tail -f /var/log/messages (which starts a live-log watching session on the designated file). Then try to add the MSE server again and keep an eye on the live log. Check if any errors are appearing (e.g.).
M.
11-11-2020 12:27 AM
i just had time to troubleshoot this again today. and i found out that the mse services is not running. i think this is the main reason why it cannot be added back to prime. but no matter how i retrieve it i.e. rebooting a few times and even restarting the vm itself it. it still doesnt want to run. when executing getserverinfo it shows:
retrieving mse services status
checking status of services at port 7555 (this same line keeps on appearing)
then will show:
failed to get the status for process at port 7555
is there any other way to make the mse services running again?
11-11-2020 12:57 AM
- Check if this document can be helpful :
M.
11-11-2020 04:43 AM
i saw that post already and the mse already has 8GB
11-11-2020 08:05 AM
- Check current status of MSE with :
# /etc/init.d/msed status
11-11-2020 08:37 PM
Hi,
below was my captured yesterday. and the line "checking status of services at port 7555" keeps appearing as well when issuing /etc/init.d/msed status.
msename]# /etc/init.d/msed status
STATUS:
Health Monitor is running
UDI: PID: AIR-MSE-VA-K9 , VID: V01, SN:msename.domainxxxx-xxx-xxxx
Disk Capacity: 407G
Disk Space used: 49G
Drive Type: Spinning Disk Drive
Server Uptime: 0 Days, 1:03 Hours
Number of Reboots:16
______________________________
Retrieving MSE Services status.
Checking status of services at port 7555
Checking status of services at port 7555
Checking status of services at port 7555
Checking status of services at port 7555
Checking status of services at port 7555
Checking status of services at port 7555
Checking status of services at port 7555
11-12-2020 02:32 AM
- As root on the mse server further check possible issues with MSE with a command as # dmesg also have an overview-look of . /var/log/messages , look for problem situations if any.
M.
12-03-2020 01:22 AM
i did the last resort which is rebuilding the mse. but this time having issue during the upgrade. creating new thread. non stop issue. *sigh*
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide