Wedge

Public area => The Pub => Support => Topic started by: havok on March 18th, 2014, 11:02 PM

Title: error 500 after server change
Post by: havok on March 18th, 2014, 11:02 PM
help
on friday i got an email from my host that they were migrating me to a different server. since then i am getting internal server error 500. i have updated my A record to point to new IP address but nothing.
is there any setting i need to change in the wedge settings
Title: Re: error 500 after server change
Post by: Pandos on March 18th, 2014, 11:24 PM
What does the fox eh... logs say?
Think this is a permission problem...
Title: Re: error 500 after server change
Post by: Bunstonious on March 19th, 2014, 04:56 AM
I am getting this same error message when I moved from an internally hosted server to a VPS.

I can confirm it is not a permissions issue (checked that) but I will do some testing on the train home.

The test I will perform is trying to install a test wedge site and see if I am missing any of the requirements.
Title: Re: error 500 after server change
Post by: Bunstonious on March 19th, 2014, 07:55 AM
Update: I was able to install a stock current version of Wedge, still get the internal server error with my main forum (I copied current files from GitHub).

Is there any way with the URL to "run it in safe mode"?
Title: Re: error 500 after server change
Post by: Bunstonious on March 19th, 2014, 12:35 PM
Starting to think it's a cache or plugin issue.

I used my test install and changed the database to my main forum and the main page loaded ok (pretty URL's broken).

What settings control the cache (eg, can you remove it and get it to rebuild)?
Title: Re: error 500 after server change
Post by: havok on March 19th, 2014, 08:08 PM
this is the response from support

On reviewing the error details when detailed errors are enabled it appears this issue is being caused by FastCGI. FastCGI settings can not be disabled or changed on a Windows hosting account. To resolve this issue you will need to either modify your scripting to no use FastCGI or switch to a Linux account if you do not have a specific need for Windows.
Title: Re: error 500 after server change
Post by: Bunstonious on March 20th, 2014, 12:57 AM
That's interesting.

I checked mine and it is using Apache Mod, not FastCGI.
Title: Re: error 500 after server change
Post by: Nao on March 20th, 2014, 06:00 PM
I'm SOOOO behind when it comes to providing tech support (Bunstonious, txcas and Wanchoppe, I think they're all waiting for my feedback on something, it's just that I don't remember what.)

I have no idea what the problem could be with FCGI, but quite honestly, last time I tried Wedge on such a server, it frigging worked....... :-/

/mehates lousy servers with weird settings.
Speaking of that, @Pandos, I know you're into fast servers... Have you tried G-Wan, from gwan.com? It's a non-open-source but free server from a Swiss team. Well, a team of one developer, with a business angel and a lawyer on top of it, apparently. This is usually not good news, but I've seen benchmarks, and apparently it's twice lighter than Cherokee, Nginx or Lighttpd. Twice.
Title: Re: error 500 after server change
Post by: Pandos on March 20th, 2014, 06:13 PM
Quote from havok on March 19th, 2014, 08:08 PM
this is the response from support

On reviewing the error details when detailed errors are enabled it appears this issue is being caused by FastCGI. FastCGI settings can not be disabled or changed on a Windows hosting account. To resolve this issue you will need to either modify your scripting to no use FastCGI or switch to a Linux account if you do not have a specific need for Windows.
Wedge has nothing to do with FastCGI. It's a backend thing.
Wedge runs on CLI or FastCGI. So there should be no problem from this side.
Title: Re: error 500 after server change
Post by: Pandos on March 20th, 2014, 06:18 PM
Quote from Nao on March 20th, 2014, 06:00 PM
Speaking of that, @Pandos, I know you're into fast servers... Have you tried G-Wan, from gwan.com? It's a non-open-source but free server from a Swiss team. Well, a team of one developer, with a business angel and a lawyer on top of it, apparently. This is usually not good news, but I've seen benchmarks, and apparently it's twice lighter than Cherokee, Nginx or Lighttpd. Twice.
Yes I know it :)
But handling is a bit  uncomfortable and I'm missing a view things.
Cherokee can stream media files out of the box. This is really important for me.
Also I love the graphical admin interface :)
But the best: Cherokee has an FrontLineCache included which is really great. You can configure it to everything you need.
Title: Re: error 500 after server change
Post by: Bunstonious on March 21st, 2014, 03:50 AM
Quote from Nao on March 20th, 2014, 06:00 PM
I'm SOOOO behind when it comes to providing tech support (Bunstonious, txcas and Wanchoppe, I think they're all waiting for my feedback on something, it's just that I don't remember what.)
I don't think I am waiting on anything else. Either you provided great support and bug fixes, or I was being retarded... lol.
Quote from Nao on March 20th, 2014, 06:00 PM
I have no idea what the problem could be with FCGI, but quite honestly, last time I tried Wedge on such a server, it frigging worked....... :-/
I am using Apache Mod PHP, same issue.
Quote from Nao on March 20th, 2014, 06:00 PM
/mehates lousy servers with weird settings.
I hope that's not directed at my server ;)

Seriously though, it's because I am in Aus... And I host myself (because I am le poor).

This particular issue happened when I went from my hosted server to my VPS, and I can confirm that I can install a fresh copy of wedge to my VPS so it meets the requirements, so I am unsure why it is giving the 500 error.
Title: Re: error 500 after server change
Post by: Nao on March 21st, 2014, 03:04 PM
It only shows up if you MOVE the data from a server to another, not if you create the data on the final server..?

Then it's a permission issue, isn't it...??!
Title: Re: error 500 after server change
Post by: Bunstonious on March 22nd, 2014, 12:42 PM
Quote from Nao on March 21st, 2014, 03:04 PM
It only shows up if you MOVE the data from a server to another, not if you create the data on the final server..?

Then it's a permission issue, isn't it...??!
Well that was suggested, but I did a CHMOD and CHOWN and CHGRP to double check that the file permissions were set correctly.

Short of a magic wand, not sure what other permission I can check :P
Title: Re: error 500 after server change
Post by: Pandos on March 22nd, 2014, 01:34 PM
Can you please put the last lines of your log here?
Title: Re: error 500 after server change
Post by: Bunstonious on March 23rd, 2014, 10:02 PM
Quote from Pandos on March 22nd, 2014, 01:34 PM
Can you please put the last lines of your log here?
Will do when I get access again. (not having proper Internet sucks)
Title: Re: error 500 after server change
Post by: Bunstonious on March 25th, 2014, 11:06 PM
So I would like to thank all of you for your help, I have worked out the issue.

Turns out that it was the Facebook plugin having an issue so I deleted all the files for it and it worked fine.

I would suggest @havok having a look at the plugins.

What's of note is that the server I am using is logging the error to the root "error.log" not the "forum-error.log" which is interesting and why it remained a mystery.

Thanks @Pandos and @Nao
Title: Re: error 500 after server change
Post by: Nao on March 26th, 2014, 07:47 AM
Did it work after disabling the plugin, or did you have to remove it entirely?
I doubt this plugin has anything to do with errors 500 though.
Were only users using facebook locked out in a 500, or everyone?
Title: Re: error 500 after server change
Post by: Bunstonious on March 26th, 2014, 08:00 AM
Literally as soon as I deleted the plugin files the forum started again.

I don't know what about it caused the issue, but the logs suggested the Facebook plugin.

Weird.
Posted: March 26th, 2014, 08:00 AM

And everyone was affected
Title: Re: error 500 after server change
Post by: Nao on March 27th, 2014, 05:23 PM
Out of interest... Can you restore the plugin files, and see if it breaks it again..?
Title: Re: error 500 after server change
Post by: havok on March 27th, 2014, 08:38 PM
i had been having issues with my host so idecided to switch rather  than wait 2 months for my renewal date on the hosting plan.
since i switched hosts from godaddy, i have had no issues
Title: Re: error 500 after server change
Post by: Bunstonious on March 27th, 2014, 10:24 PM
Quote from Nao on March 27th, 2014, 05:23 PM
Out of interest... Can you restore the plugin files, and see if it breaks it again..?
Hopefully I will have the internet connected today so might be able to try.

Sorry for hijacking the thread @havok
Title: Re: error 500 after server change
Post by: Kian on July 24th, 2018, 02:52 PM
Quote from Nao on March 21st, 2014, 03:04 PM
It only shows up if you MOVE the data from a server to another, not if you create the data on the final server..?

Then it's a permission issue, isn't it...??!
Yes, I actually just migrated from my last work to a VPS at OVH restoring my last backup.

Whenever I post a message, I get this server error (Apache code 500), though the messages is correctly posted.

Still trying to figure this out.
I may be missing mods or having permission issues.


Code: [Select]
192.168.168.10 - - [24/Jul/2018:14:53:45 +0200] "POST /?board=22;action=post2 HTTP/1.1" 500 434 "http://test.potesnroll.com/?topic=1090.msg207397" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36"



I could be missing a module :

Code: [Select]
root@vps569571:/etc/apache2/mods-available# ls
access_compat.load  authnz_fcgi.load      cern_meta.load     dump_io.load       lbmethod_bybusyness.load  mpm_prefork.conf     proxy_ftp.conf       rewrite.load           status.conf
actions.conf        authnz_ldap.load      cgid.conf          echo.load          lbmethod_byrequests.load  mpm_prefork.load     proxy_ftp.load       sed.load               status.load
actions.load        authz_core.load       cgid.load          env.load           lbmethod_bytraffic.load   mpm_worker.conf      proxy_hcheck.load    session_cookie.load    substitute.load
alias.conf          authz_dbd.load        cgi.load           expires.load       lbmethod_heartbeat.load   mpm_worker.load      proxy_html.conf      session_crypto.load    suexec.load
alias.load          authz_dbm.load        charset_lite.load  ext_filter.load    ldap.conf                 negotiation.conf     proxy_html.load      session_dbd.load       unique_id.load
allowmethods.load   authz_groupfile.load  data.load          file_cache.load    ldap.load                 negotiation.load     proxy_http2.load     session.load           userdir.conf
asis.load           authz_host.load       dav_fs.conf        filter.load        log_debug.load            php7.0.conf          proxy_http.load      setenvif.conf          userdir.load
auth_basic.load     authz_owner.load      dav_fs.load        headers.load       log_forensic.load         php7.0.load          proxy.load           setenvif.load          usertrack.load
auth_digest.load    authz_user.load       dav.load           heartbeat.load     lua.load                  proxy_ajp.load       proxy_scgi.load      slotmem_plain.load     vhost_alias.load
auth_form.load      autoindex.conf        dav_lock.load      heartmonitor.load  macro.load                proxy_balancer.conf  proxy_wstunnel.load  slotmem_shm.load       xml2enc.load
authn_anon.load     autoindex.load        dbd.load           http2.load         mime.conf                 proxy_balancer.load  ratelimit.load       socache_dbm.load
authn_core.load     buffer.load           deflate.conf       ident.load         mime.load                 proxy.conf           reflector.load       socache_memcache.load
authn_dbd.load      cache_disk.conf       deflate.load       imagemap.load      mime_magic.conf           proxy_connect.load   remoteip.load        socache_shmcb.load
authn_dbm.load      cache_disk.load       dialup.load        include.load       mime_magic.load           proxy_express.load   reqtimeout.conf      speling.load
authn_file.load     cache.load            dir.conf           info.conf          mpm_event.conf            proxy_fcgi.load      reqtimeout.load      ssl.conf
authn_socache.load  cache_socache.load    dir.load           info.load          mpm_event.load            proxy_fdpass.load    request.load         ssl.load
root@vps569571:/etc/apache2/mods-available# ls ../mods-enabled/
access_compat.load  auth_basic.load  authz_core.load  autoindex.conf  deflate.load  env.load     mime.load         negotiation.conf  php7.0.load      setenvif.conf  status.load
alias.conf          authn_core.load  authz_host.load  autoindex.load  dir.conf      filter.load  mpm_prefork.conf  negotiation.load  reqtimeout.conf  setenvif.load
alias.load          authn_file.load  authz_user.load  deflate.conf    dir.load      mime.conf    mpm_prefork.load  php7.0.conf       reqtimeout.load  status.conf
root@vps569571:/etc/apache2/mods-available#
Title: Re: error 500 after server change
Post by: Kian on July 27th, 2018, 10:05 AM
Nevermind, I repaired my old server :-)
Title: Re: error 500 after server change
Post by: Nao on August 22nd, 2018, 06:21 PM
Oh, good then!