HELP! New ISPConfig Upgrade Messed up server!

I was alerted to the new update of ISPConfig 3.0.4 and updated it. Now I cannot access the CPanel. All browers show "not found" still using port :8080
Luckily the sites are running, and I was able to access phpMyAdmin from the URL. Tried to do a DB repair to no avail. Still can't access CPanel.

Also, amavisd is just GONE! The mail server was working brilliantly until the update. Now Linux does not even recognize amavisd as a service.

/etc/init.d/amavisd (with no action) So I run this with "start". The outcome is:

Starting amavisd: drop_priv: No such username:

The second outcome is not available anyway, because I have never used apache2 for any commands so it is not recognized. Only httpd is recognized, so I simply followed the path in the root SSH file path like so:

/etc/httpd/conf/sites-available

Where usually my webserver is listed last, but is no longer there. What are the best ways to fix / repair amavisd and repair the webserver under "sites-available"?

Ok, with the upgrade, I was alerted to it in the admin CPanel, so I elected to click the link under "System" (bottom left), to upgrade / update IPSConfig. It asked if I was sure. I clicked to continue and was given a message that the update was under way.

Without giving you the HD output, no, I have TONS of storage on this server. I am currently using about 17% of 1.3 TB (Includes OS)

In general it is always better to install updates on the shell as you would see if a error occurs then. The update procedure for every release is outlined in the release notes of that release which are availble on ispconfig.org and here in the forum. What you can try now is to redo the update on the shell. But first, you should make a backup of the /etc and ispconfig directory. Execute tehse commands as root user on the shell:

Maybe Till will get this?
Since the upgrade of ISPConfig 3 to 3.0.4, I have been able to repair amavisd, but still get a 500 internal server error when trying to access ISPConfig CPanel on port 8080. I have checked log after log, and this is the only thing that I find (that fits the upgrade time frame). Repeated error:

Maybe Till will get this?
Since the upgrade of ISPConfig 3 to 3.0.4, I have been able to repair amavisd, but still get a 500 internal server error when trying to access ISPConfig CPanel on port 8080. I have checked log after log, and this is the only thing that I find (that fits the upgrade time frame). Repeated error:

Well, nothing is working for me repairing the system. This is a lesson learned that I should have learned long ago. Never jump on an update just because it's there. Wait for about three months until all the dummys like myself have been the ginny pigs on update bugs, crashes, etc., until the release is stable. Hard lesson learned. Lots to fix....don't know where to start.

The biggest note: Don't place an "upgrade" link inside of any software design when you don't know or intend for it to function perfectly. If your original intent is for any upgrade to perform at its best through SSH, remove the option to update by CPanel.