Author Topic: "Service Currently Not Available!"  (Read 6641 times)

Offline markcausa

  • Newbie
  • *
  • Posts: 2
"Service Currently Not Available!"
« on: November 22, 2006, 08:23:42 PM »
Hello everyone! Can anyone tell what exactly went wrong with my installation by looking at this?
http://www.phirefast.com/roundcube/

I ran the right "/SQL/x.initial.sql" file. So does anyone know what error #1f4 is?

Thanks! :D

Update: I just did the modifications to the CONFIG files in the directory and now I'm getting a blank page at the link above. When I look in the MYSQL DB, I see there are no tables in there, so something in the link between the installation and MYSQL DB didn't work.

Offline daashag

  • Full Member
  • ***
  • Posts: 198
Re: "Service Currently Not Available!"
« Reply #1 on: November 22, 2006, 09:53:22 PM »

Offline markcausa

  • Newbie
  • *
  • Posts: 2
Re: "Service Currently Not Available!"
« Reply #2 on: November 22, 2006, 10:51:42 PM »
That didn't do the trick. Thank you very much for the link.

In the /config/db.inc.php file, I think there is a problem with the MySQL link up. :-\

Offline daashag

  • Full Member
  • ***
  • Posts: 198
Re: "Service Currently Not Available!"
« Reply #3 on: November 23, 2006, 08:31:46 AM »
What exactly is your problem? Blank Page or service currently not available.

Offline fuerst

  • Newbie
  • *
  • Posts: 2
Re: "Service Currently Not Available!"
« Reply #4 on: November 28, 2006, 07:26:56 AM »
Today one user was not able to login because he got "SERVICE CURRENTLY NOT AVAILABLE! - Error No. [1f4]". At the same time I was able to login and to use Roundcube. There is no PHP error log entry, no IMAP login problem. Very strange. Any idea how to trace this error?

Offline edoceo

  • Newbie
  • *
  • Posts: 3
Re: "Service Currently Not Available!"
« Reply #5 on: November 28, 2006, 01:34:44 PM »
I was having this issue on my first install.
My first issue was that my DNS was all buggered up and in that case nobody could log in.
Can you trace the SQL statements (log_statement = all in postgres) to see if maybe an insert into 'users' is failing?

Also 14f hex = 500 dec, lots of the raise_error() calls use 500 so you could find those and change to 501, 502 or whatever to see which specific error is hitting.

Also in my codebase I've added lots of this stuffs
 write_log('trace',print_r($x,true));
I get lots of stuffs in ./logs/trace

Because the system is AJAX based things like
 print_r($x);
 exit;
don't work cause the response is sent on the side channel, not the main HTTP connection so you'll have to use write_log() to trace. HTH.