Missing styles & can't log into index.pl

[lamarchk]

Hi!

This is my first time posting here.

I seem to have the same problem as with the guys from the email thread.

I have tried all directions from the previous posts but it seems that its not helping me resolve the issue at hand.

under /var/log/httpd/access_log and error_log there are no problems.

Earlier from the day only one of us ITs can access the OTRS service, while all of us are all locked out and we are getting this screen from our browser.

NoCss.png

I am at a bind now. I would like to have this resolved the earliest possible time.

Thank you in advance.

[wurzel]

Hi,

version?
new install?
upgrade?
own skin?
own theme?
code changes?

/var/log/syslog ?
/var/log/messages?

browser version?

Florian

[lamarchk]

Hi Florian (?)

Thanks for the reply.

Here's the necessary details you have asked.

version? 3.1.12
new install? Nope
upgrade? Yes, from version 2.x
own skin? Nope
own theme? Nope
code changes? No code changes from the front end, I think we have updated Ticket.pm a year ago.

/var/log/syslog ? Using rsyslog
/var/log/messages? No critical errors

browser version? Updated Opera and Chrome

[lamarchk]

If it may help

I have run majority of the fixes described on this post from otterhub.

viewtopic.php?f=62&t=7809&p=105105#p105105

I am not sure since the last was from way back last year.

[jojo]

did you:

- check disk space?
- rebuild all caches?
- rebuld config (as OTRS user)?
- restarted apache?

[lamarchk]

Hi jojo.

did you:

- check disk space? yes



Would you have any recommended fix for this?

- rebuild all caches?



- rebuld config (as OTRS user)? How do you do this (I am still an OTRS newbie)

- restarted apache? Yes, countless times unfortunately

[RStraub]

- rebuld config (as OTRS user)? How do you do this (I am still an OTRS newbie)

There's a script to do that for you:
otrs/bin/otrs.RebuildConfig.pl

Though on our machines it breaks file permissions and we have to change the ZZZAuto.pm

I'd recommend that you "tail -f" the apache log while trying to access the index.pl. From my experience the browser-too-old warning has to do with file permissions.

Best regards,
Rolf

[jojo]

the rebuild conif script needs to be run with the OTRS user.

your diskspace is not sufficient, check the disk and get more space!

[lamarchk]

I seem to have lost my password for the "otrs" user.

would it be okay to have it changed? will i have problems with mysql?

[RStraub]

I seem to have lost my password for the "otrs" user.

would it be okay to have it changed? will i have problems with mysql?

You'll get problems if you change the mysql password.

Can't you "su" to the otrs user?

[jojo]

try sudo -u otrs /opt/otrs/bin/otrs.RebuildConfig.pl

[lamarchk]

Sir Jojo,

I am still at the process of getting the necessary space back from mysql and httpd.



Just recently I have just removed non-moving old log files from /var/log/httpd and /var/log. which may have caused this. though i am not sure. since after umounting the / and rebooting the server i am still getting this from df -h



as this has been what I have been doing if ever we can't access index.pl. But now we can't access everything from OTRS except the customer.pl.

would you have any ideas on how would i my free space back?

Thank you in advance.

[crythias]

58GB with 133MB free is better than nothing.

from the mountpoint,

Code: Select all

du -h --max-depth=2

Might help determine what folders have large space usage. As you've guessed, probably logs might be high on the list. After that, it's possible that large installs or attachments, .zip files, .pdfs or .tar.gz files (likely in /home/user or /root) or extracted version of same.

This is more something outside the boundaries of OTRS to resolve. It's very likely you have additional database issues that might need checking or repairing. May be a good idea to check backups.

[lamarchk]

Sir's crythias, jojo and RStraub,

We have resolved the issue by re-installing the whole OTRS system.

We tried upgrading to 3.3.1, 3.3.2, and 3.2.1. But upgrading to 3.1.2 from 3.1.12 did the trick.

Thanks for the great help. Probably next time we would get the hang of resolving this issue.

Upon upgrading we didn't copy the old /var folder to the new one. Which might have fixed the issue altogether.

Thanks again.