OpenScape4000 V8

[R.Hussain]

Hi Guys,

I have OpenScape4000 V8. its Assistant and portal are not accessible showing " login user incorrect ". Although username and password is correct. Before this a message was displayed " var patriation is 92% and on 95% all assistant features will be blocked".

Is there any solution to recover/access the assistant and portal without the re-installation of whole system.

Thanks

 

[Moriendi]

Assistant will eventually reinstall itself if partition usage becomes too high. Is it possible it has reinstalled and it's now on the default password? If there is no backup it will all be default.

 

[R.Hussain]

Hello Moriendi,

Thanks for your quick response. I thought so before, but unfortunately Assistant did not install automatically as i already checked by entering default password. Is there any way we access Assistant through linux.

 

[Moriendi]

Might be worth rebooting the node with the ADP on so Assitant reboots on the other node.

 

[R.Hussain]

I have already re-booted the whole system but no change found. When i try to access the system through SSH by putty, when enter password, it shows " Access denied" what you suggest next ? please .

 

[Moriendi]

What default login did you use?

 

[R.Hussain]

User Name = engr
Password = 4K-admin

 

[Moriendi]

If you login as root to the host eth0 IP (or Portal) what does df -kh look like? Any full partitions?

 

[R.Hussain]

Hello Moriendi,

Portal is not accessible with user Root. However with user root on eth0 (linux shell) result is attached.

 

[Moriendi]

I was looking for a full Assistant partition but that looks OK.
Normally in this situation you would login to Portal and start an Assistant reinstallation.
But if you can't login to Portal, you do have a problem.
So you can't login to Assistant on ssh with engr either ?

 

[sbcsu]

If you can log on using Putty then go to /var/log
If there are a lot of messages.bz2 and messages.log
then you can delete them
rm messages*.bz2
rm messages*.log
this will free up space
Connect to eth0 on both and assistant

leave the 'messages' file there because it is being written to
Verify that the /var partition is not full with df -m

 

[R.Hussain]

Dear Moriendi and sbcsu,

I appreciate your valuable input but this can be done when your portal is under control. Both the VM Assistant & Portal not accessible. My question is:- Is there any way ?. that from Linux shell i can access the Assistant var partition log files, remove unwanted log files, messages, create the space and re-start the Assistant. May be it resolve the problem.

 

[Moriendi]

What happens when you try ssh to Assistant? You didn’t say. If you can login there, check free space like above.

Assistant problems are normally separate from Portal
though.

I would reboot the node which is running ADP so Portal loads on other node and try Portal again. If you can login to Portal you can reinstall Assistant.

Free space would be interesting to see on Assistant because it does reinstall itself if disk becomes full so we could see then if it had reinstalled itself.

 

[R.Hussain]

1. When i access Assistant through SSH, on entering password, it shows " Access denied".

2. I think that both Portal and Assistant are on the same VM. login user name and password are the same. that is why it could not accessed when i restarted the system previously.

3. You are right, assistant should be install automatically but till the time it didn't. How much time will it take to start the process after var partition is full. Almost 5 days elapsed when i saw the issue first time.

 

[Moriendi]

They are not on the same VM. In fact Portal is not on any VM.

You can check Assistant log by reading file Assisant-console.log.
Depending on your software version, it's in either /var/log/libvirt/qemu or /var/log/ha.
cat that file for anything useful.

 

[R.Hussain]

Hello Moriendi,

Assistant-console.log is attached

 

[Moriendi]

You can see it reinstalled and restored an old backup.


Restoring Assistant-Data from 2022-05-17 12:41 ... |-- 2024 Jan 29 22:44:01 OGDCL-SYS1 --||-- 2024 Jan 29 22:52:03 OGDCL-SYS1 --| done



Is it possible you need to use an older password?

 

[R.Hussain]

Dear Moriendi,

Thank you very much for prompt response and kind support. Issue has been resolved.

Once again so nice of you