tracing errors/log files?

[davout]

Is there a way to have CMS-MS dump errors into a log file? 

I've installed CMS-MS into my remote Java hosting service.  After logging into the admin area, if I try to add a new content page the process fails and the web app jumps to the login page.

Obviously something is seriously wrong. How can I switch on debugging/logging to trace the cause?

[Dr.CSS]

Most host/servers make error logs that are in the root of site/install, you can also maybe turn on some debug stuff in the config.php, you may also want to look at your system information page to see if you have any yellow ! or red X...

[davout]

What system information page?

Most host/servers make error logs that are in the root of site/install, you can also maybe turn on some debug stuff in the config.php, you may also want to look at your system information page to see if you have any yellow ! or red X...

[davout]

Here's the text extract from the System Information page...

Code: Select all

Cms Version: [b]1.6.6[/b]

Installed Modules:

CMSMailer: [b]1.73.14[/b]
FileManager: [b]1.0.1[/b]
MenuManager: [b]1.6.2[/b]
ModuleManager: [b]1.3.1[/b]
News: [b]2.10.3[/b]
nuSOAP: [b]1.0.1[/b]
Printing: [b]1.0.4[/b]
Search: [b]1.6.1[/b]
ThemeManager: [b]1.1.1[/b]
TinyMCE: [b]2.5.5[/b]
FrontEndUsers: [b]1.6.11[/b]
Forum: [b]0.9.2[/b]
CGExtensions: [b]1.17.6[/b]
NMS: [b]2.2.3[/b]


Config Information:

php_memory_limit: [b][/b] 
process_whole_template: [b]false[/b] 
max_upload_size: [b]32000000[/b] 
default_upload_permission: [b]664[/b] 
assume_mod_rewrite: [b]false[/b] 
page_extension: [b][/b] 
internal_pretty_urls: [b]false[/b] 
use_hierarchy: [b]true[/b] 


Php Information:

phpversion: [b]5.2.13[/b] 
md5_function: [b]On[/b] (True) 
gd_version: [b]2[/b] 
tempnam_function: [b]On[/b] (True) 
magic_quotes_runtime: [b]Off[/b] (False) 
memory_limit: [b]64M[/b] 
max_execution_time: [b]60[/b] 
safe_mode: [b]Off[/b] (False) 
session_save_path: [b]/tmp[/b] (1777) 
session.use_cookies: [b]On[/b] (True) 


Server Information:

Server Api: [b]cgi-fcgi[/b] 
Server Db Type: [b]MySQL (mysql)[/b] 
Server Db Version: [b]5.0.89[/b] 

Most host/servers make error logs that are in the root of site/install, you can also maybe turn on some debug stuff in the config.php, you may also want to look at your system information page to see if you have any yellow ! or red X...

[davout]

The only red or yellow entry is...

      0777 
      config.php writable. It is more safe if you change permission to read-only

Everything else is green or unmarked

[JeremyBASS]

The config file has the line for debug... set to true and you'll see the debug report and you can lok for the error if it's there..as far as the 777 on the config, yes it's wise to pull it back to 655 in between edits.  Also you should refer to the server logs... HTH Cheers -Jeremy

[davout]

Is there a way to redirect the debug output to a log file?

when I try to add a new content page on clicking the 'submit' button it now returns me to the add page form.  All the debug lines shown at the end of this form have 'error 0'.

[davout]

where will I find the server logs?

[davout]

An error found in 'error-Log' ....

Code: Select all

[30-Mar-2010 18:58:45] PHP Warning:  Adding option (Name: open_basedir Value: ) (12, 0) failed!
 in Unknown on line 0

Any ideas?

[JeremyBASS]

call your host and ask them to trun off open_basedir ... that should help... it may-be faster to say what the error is?  HTH -J

[davout]

Don't think I can do that, as I'm using a shared server.

What does this error infer?  Also, I asked about redirecting all the debug log output to a file, is this possible?

[JeremyBASS]

What does this error infer?<<well the short is that some modules will not work.

Also, I asked about redirecting all the debug log output to a file, is this possible?<<Not atm.. but I love the idea... Make a feature quest in the Forge. 

[davout]

None of this helps my situation.