Upgrade from 18.03 to 18.04/05 fails

[Twonky]

Hi,

while trying to upgrade from 18.03 with UI the update to 18.04 is offered. When trying to update via UI i get en exit error 1 with nothing else. Is there some log i can have a look why this fails?

In parallel i tried the upgrade via console:
replaced the sources-file entries from 1803 with 1805. Die apt update/upgrade during the process everything seems to work, but i can't login to the webinterfac afterwards. It says "Server error" during login.
What i noticed is that during upgrading the 3cx-Package the console kept saying: sudo - password required
Also here, is there a place where i can find the logs from this process?

Any help is apreciated.

Thanks

 

[bitn2]

You missing a lot of informations... Debian or Windows based... Virtualised or not... How did you installed your 3cx? etc...To use the cli to upgrade your 3cx is always the last way to go.

 

[Twonky]

Thanks for your reply.

The installation is a virtualised, debian based setup. It was upgraded from an V16 installation quite a while ago.

Regards

 

[TheodorosG_3CX]

How was the PBX previously installed? Was it with 3CX ISO or via commands?

 

[cobaltit]

I would just backup, copy the backup off and then do a fresh install from the latest ISO and restore. You have an older setup which sounds like it has something off.

 

[Twonky]

It was upgraded from an V16 via CLI. I'd really understand whats going on.
Does the system really produce no logs during setup?

Thanks

 

[bitn2]

It was upgraded from an V16 via CLI. I'd really understand whats going on.
Does the system really produce no logs during setup?

Thanks

Upgrade via cli could be the problem. Thats not the supportet way. Get a backup and reinstall like @cobaltit said.

 

[Twonky]

Thank you. I completely understand the supported way of backup/restore.
I don't want to offend someone, but my initial question was, if/where are log-files located that are possibly produced during the installation process. I'd really understand _why_ something happens. At least it seems that i have an easy way to fix this...

Regards

 

[bitn2]

There should be something in the debian logs... But i would just reinstall the pbx. Time is money ;-)

 

[Nathan@Voxtelesys]

Your logs have likely rotated, but some places to check:

You can use tail -f , cat , less to view the .log files.

/var/log/apt/term.log /var/log/apt/history.log /var/log/apt/ (rotated logs will show as "*.1.gz" and would need to be unziped)
/var/log/syslog/ /var/lib/3cxpbx/Instance1/Data/Logs/

Other things to check:
journalctl -xe or dmesg
systemctl status 3CX*

A couple of ideas:
- Clear your browser cache or use Private/Incognito browsing window
- You mention having to type in sudo password several times, do you think you missed one and let the prompt time out? Could you login to the root account and then run your apt update/upgrade cmd's?

Since the system is already broken what happens when you try to update again?

What version does it say you are on currently? apt list policy -a 3cxpbx

As all above have said, quickest way to get back up and running is restoring a backup to the official ISO.

I hope this helps, let us know how it goes!