RESOLVED - Site stopped working

For questions and problems with the CMS core. This board is NOT for any 3rd party modules, addons, PHP scripts or anything NOT distributed with the CMS made simple package itself.
Post Reply
bullarab
Forum Members
Forum Members
Posts: 12
Joined: Fri Nov 09, 2007 2:05 pm

RESOLVED - Site stopped working

Post by bullarab »

Hello all

The URL is http://www.bullarab.com.au/
CMSMS was working fine until recently, when about 10 days ago or there abouts it stopped displaying pages, they just come up blank.

You can login to the admin section and all the content is there to be edited, but when trying to view the site nothing displays.
Below is the error we are now gettiing - 500 Internal Server Error
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@bullarab.ozziedoggers.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/1.3.37 Server at bullarab.ozziedoggers.org Port 80
the cpanel logs also had error -

a premature end of script

Any advice will be much appreciated  ;)
Last edited by bullarab on Fri Nov 16, 2007 5:07 am, edited 1 time in total.
unknown

Re: Site stopped working

Post by unknown »

Hello,
I'm going to take a chance here, and refer you to this thread:
http://forum.cmsmadesimple.org/index.ph ... 772.0.html
Your situation seems quite like it. (likely permissions).

HTH, and best wishes.
User avatar
kermit
Power Poster
Power Poster
Posts: 693
Joined: Thu Jan 26, 2006 11:46 am

Re: Site stopped working

Post by kermit »

double-check your pretty url/mod_rewrite configuration (config.php and .htaccess). also, if you've got php_flag entries in htaccess, try commenting them out (if you're running php as cgi, leave them commented out).

double-check permissions on files & folders.. your cpanel server may be set up to NOT permit scripts to run if they (or the directory they're in) are writable by 'group' or 'other' if you're using php/cgi (and scripts run as your user, not the webserver)... you'll see entries in your error log referring to writable scripts if this is the case (error: directory is writable by others)  the umask test in global configuration will tell you what user cmsms scripts are running as.
eternity (n); 1. infinite time, 2. a seemingly long or endless time, 3. the length of time it takes a frozen pizza to cook when you're starving.
4,930,000,000 (n); 1. a very large number, 2. the approximate world population in 1986 when Microsoft Corp issued its IPO. 3. Microsoft's net profit (USD) for the quarter (3 months) ending 31 March 2007.
CMSMS migration and setup services | Hosting with CMSMS installed and ready to go | PM me for Info
bullarab
Forum Members
Forum Members
Posts: 12
Joined: Fri Nov 09, 2007 2:05 pm

Re: Site stopped working

Post by bullarab »

Thanks for the reply people

firstly, what permissions should the folders/files have

secondly, in the link above it mentions a PHP error file, how do i create this, i did a search but didnt see anything to elighten me

:-[

please bear with me, ive not used CMSMS much at all.
streever

Re: Site stopped working

Post by streever »

did you try going into admin and clearing site cache?
unknown

Re: Site stopped working

Post by unknown »

bullarab wrote: firstly, what permissions should the folders/files have

Code: Select all


/tmp - 0777

all others - 0755 should work in most cases, but other
possibilities would include 0754, and 0744
Your config.conf file (after setup) should be 0444

How do I make these changes, you ask?
In your web sites root folder -

Code: Select all


chmod -R 0755 .
cd tmp
chmod -R 0777 .

Now, please understand that the folders all need to be
owned and operated by your web server.
If your web server's identity is www (most cases)
From your web servers root -

Code: Select all


chown -R www:www .

DONE! all permissions are fixed, and correct. :)
bullarab wrote: secondly, in the link above it mentions a PHP error file,
how do i create this, i did a search but didnt see anything to elighten me
PHP settings are all controlled by the declarations in your
php.ini file, or your .htaccess file
The settings related to error loggings are as follows

Code: Select all


log_errors = On/Off
log_errors_max_len = <byte length max> - maximum size in bytes logged for each error
error_log = /full/path/to/error/file/including/error/file/name

This is most probably all the information you would require. :)


bullarab
Forum Members
Forum Members
Posts: 12
Joined: Fri Nov 09, 2007 2:05 pm

Re: Site stopped working

Post by bullarab »

Ive set all permissions to 755 except tmp which is 777

Cleared the cache, still comes up with error above, or if u put index.php in the address bar after the URL it comes up a blank page with no error

config.php says the following



Global Settings in the admin panel)
#after making any changes to path or url related options

#-----------------
#Database Settings
#-----------------

#This is your database connection information.  Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = 'localhost';
$config['db_username'] = '-----------';
$config['db_password'] = '********';
$config['db_name'] = 'ozzie3_bullarab';

#If app needs to coexist with other tables in the same db,
#put a prefix here.  e.g. "cms_"
$config['db_prefix'] = 'cms_';

#Use persistent connections?  They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;

#Use ADODB Lite?  This should be true in almost all cases.  Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;

#-------------
#Path Settings
#-------------

#Document root as seen from the webserver.  No slash at the end
#If page is requested with https use https as root url
#e.g. http://blah.com
$config['root_url'] = 'http://www.bullarab.com.au';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/home/ozzie3/public_html/bullarab';

#Name of the admin directory
$config['admin_dir'] = 'admin';

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/home/ozzie3/public_html/bullarab/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = '/home/ozzie3/public_html/bullarab/uploads';

#Where is the url to this uploads directory?
$config['uploads_url'] = $config['root_url'] . '/uploads';


#---------------
#Upload Settings
#---------------

#Maxium upload size (in bytes)?
$config['max_upload_size'] = 2000000;

#Permissions for uploaded files.  This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';

#------------------
#Usability Settings
#------------------

#Allow smarty {php} tags?  These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;

#CMSMS Debug Mode?  Turn is on to get a better error when you
#see {nocache} errors.
$config['debug'] = false;

#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;

#------------
#URL Settings
#------------

#Show mod_rewrite URLs in the menu? You must enable 'use_hierarchy' for this to work for modules
$config['assume_mod_rewrite'] = false;

#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';

#If you don't use mod_rewrite, then would you like to use the built-in
#pretty url mechanism?  This will not work with IIS and the {metadata} tag
#should be in all of your templates before enabling.
$config['internal_pretty_urls'] = false;

#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy?  (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = false;

#If using none of the above options, what should we be using for the query string
#variable?  (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';

#--------------
#Image Settings
#--------------

#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';

#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/home/ozzie3/public_html/bullarab/uploads/images';
$config['image_uploads_url'] = $config['root_url'] . '/uploads/images';


#------------------------
#Locale/Encoding Settings
#------------------------

#Locale to use for various default date handling functions, etc.  Leaving
#this blank will use the server's default.  This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';

#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8.  If you'd like this to be different, change
#both.  Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding.  This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = '';
$config['admin_encoding'] = 'utf-8';

#---------------------------------------------
#Use the old stylesheet logic?  It's much slower, but it works with older
#versions of CMSMS.  You'll also need this set to true if there is a module
#that uses a stylesheet callback.  Leave it as false instead you really
#need it.
$config['old_stylesheet'] = false;

# URL of the Admin Panel section of the User Handbook
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php ... dmin_Panel';

#Enable backwards compatibility mode?  This basically will allow some
#modules written before 1.0 was released to work.  Keep in mind that this
#will use a lot more memory and isn't guaranteed to fix the problem.
$config['backwards_compatible'] = false;

#Not used anymore... kept around, just in case
$config['disable_htmlarea_translation'] = false;
$config['use_Indite'] = true;
?>
I should also say, we had a domain name pointed to the server we host this from, that domain name was pointed elsewhere and the site above was a subdomain of the first one, but had its own domain name whcih was pointed at that folder.

To gain access to the server once our primary DN had been changed, the host gave us another subdomain that we could use to login to CPanel as they had moved us off a prod server. This was about the time it went pear shaped

not sure if that might help, but i still have issues
unknown

Re: Site stopped working

Post by unknown »

OK, while it's interesting information about the DN change, and while it is possible but unlikely
this itself is the problem. It isn't any easier to diagnose the problem if the only error information
available is a generic Apache 500 message. This was the reason for going through the trouble
of explaining how to obtain error messages. This information was not so much to inform you how to
create/obtain the error information for yourself. But rather, so you could share that information with
us. That way someone will get the information needed to solve your problem. In addition
to the PHP_ERROR log, and Apache ERROR log would also be of great benifit. So please, do
share the error messages returned by PHP, and Apache. This will insure the fastest return on
a working CMSMS for you. :)

Best wishes. :)

P.S. On a hunch, I'll bet you find lines from your .htaccess file in your Apache error log, stating
something to the effect: blah, blah not allowed here, or server access prohibits ...

kermit already alluded to the .htaccess file.

but I'll suggest in the short term - not a good solution, but may give a clue -
rename .htaccess to _htaccess.
Last edited by unknown on Sun Nov 11, 2007 11:23 am, edited 1 time in total.
bullarab
Forum Members
Forum Members
Posts: 12
Joined: Fri Nov 09, 2007 2:05 pm

Re: Site stopped working

Post by bullarab »

i renamed the HTAACCESS file the other day in the bullarab folder and it did not make a difference, HOWEVER there is another htaccess file in the root of the server which has text in it... do u mean this one? as i have renamed both and no joy

i will do the other suggestions above and see what i can get for you guys

cheers
unknown

Re: Site stopped working

Post by unknown »

bullarab wrote: i renamed the HTAACCESS file the other day in the bullarab folder and it did not make a difference, HOWEVER there is another htaccess file in the root of the server which has text in it... do u mean this one? as i have renamed both and no joy

i will do the other suggestions above and see what i can get for you guys
cheers
HOWEVER there is another htaccess file in the root of the server which has text in it... do u mean this one?
Absolutely yes. Especially the one in your root folder, and any other .htaccess file you can find.
i will do the other suggestions above and see what i can get for you guys
We wait with baited breath. ;)

Best of luck to you.
bullarab
Forum Members
Forum Members
Posts: 12
Joined: Fri Nov 09, 2007 2:05 pm

Re: Site stopped working

Post by bullarab »

ok...

I have edited the only PHP.iNI file which is located undre teh public_html folder on the server with the following
register_globals = on

[Zend]
zend_optimizer.optimization_level=15
zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-2.5.10
zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-2.5.10
zend_optimizer.version=2.5.10a
zend_extension = /usr/local/lib/ioncube_loader_lin_4.4.so

zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so
zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so

log_errors = On
log_errors_max_len = 65000
error_log = /home/ozzie3/logs/errors.txt
i have renamed all .htaccess files, to no avail

now as for the logs, i dont seem to be able to view any logs in cpanel, in fact it says in file manager the folder is missing. I can only think this is due to us being on a non prod server where logs are not avail.
unknown

Re: Site stopped working

Post by unknown »

Hello,
I would recommend you use the following:

Code: Select all


<IfModule mod_php4.c>
    php_value error_log /home/ozzie3/logs/errors.txt
    php_flag log_errors On
    php_value log_errors_max_len 65000
</IfModule>

in your /.htaccess file
NOTE: that the IfModule tag above assumes a PHP 4 install. Change as required.

Another possibility would be to use an @ini_set value in the include.php file located in your
CMSMS  / folder.
You might also need to change from path values to using a related path
as in:

Code: Select all


    php_value error_log ~/logs/errors.txt

Just for kicks, why don't you use the name php_errors.txt just for clarity. :)

IMPORTANT:
no matter what, you MUST ensure that the log folder exists, that the log file exists,
that the web server Read, Write, and Execute permissions on the log folder,
and log file BEFORE attempting these settings - else it all will surely fail.


Best wishes.
Pierre M.

Re: Site stopped working

Post by Pierre M. »

Hello,

if you don't have the access.log it isn't web hosting.
if you don't have the error.log it is impossible to debug.
Have these logS. Ask your hoster about them and about the change in your site.

Pierre M.
bullarab
Forum Members
Forum Members
Posts: 12
Joined: Fri Nov 09, 2007 2:05 pm

Re: Site stopped working

Post by bullarab »

hi all

well it seems the host had moved us onto another server but had not updated their dns records to reflect it, hence why the logs stopped working when i started posting above.

They have fixed up the problem, and now all is working fine, thank you all for your assistance.

now onto the wordpress issue i have... lol  :D
Post Reply

Return to “CMSMS Core”