RUEI 6.5.1 is installed successfully without any error.
While trying to access RUEI url, login screen shows error as in following screenshot:
An internal system error is seen in /ruei/var/opt/ruei/processor/log/websensor*dbg file and this error is thrown even before showing login prompt screen.
Exception: An internal system error has occurred. Please contact the Administrator with the error details.
Code: 256
Stack trace: #0 /ruei/opt/ruei/gui/include/data/monitoring.inc.php(3566): uxQuery->Execute()
#1 /ruei/opt/ruei/gui/proxy.php(829): utGetNotificationProfile(1001)
#2 {main}
Action:
Verify the permission of $RUEI_DATA directory.
Ensure that 'apache' user has read permission for $RUEI_DATA directory so that it can read the oracle wallet.
%chmod 750 $RUEI_DATA
While trying to access RUEI url, login screen shows error as in following screenshot:
An internal system error is seen in /ruei/var/opt/ruei/processor/log/websensor*dbg file and this error is thrown even before showing login prompt screen.
Exception: An internal system error has occurred. Please contact the Administrator with the error details.
Code: 256
Stack trace: #0 /ruei/opt/ruei/gui/include/data/monitoring.inc.php(3566): uxQuery->Execute()
#1 /ruei/opt/ruei/gui/proxy.php(829): utGetNotificationProfile(1001)
#2 {main}
Action:
Verify the permission of $RUEI_DATA directory.
Ensure that 'apache' user has read permission for $RUEI_DATA directory so that it can read the oracle wallet.
%chmod 750 $RUEI_DATA
4 comments:
Thanks!
Wasn't mentioned in the manual, was it?
Manual mentions about having appropriate permissions for the given directory. But sometime we do miss steps and I observed it in one of the installations.
Old thread, nevertheless a frequent occurring topic. So, as a placeholder, here's how I solved mine.
Apparently, some versions of RUEI have a challenging step in the manual. (If you read the PDF version that is...)
Make sure not to forget about the step to add the following line to your /etc/sysconfig/httpd
source /etc/ruei.conf
If you forget about that line, it'll throw up the same error message, though with a little different debug analysis.
Spent a day on solving this riddle...
Thanks for additional info.
Post a Comment