Home › Blogs › parakletos's blog

SIYE

Tue, 10/13/2009 - 18:01 — parakletos

    Anyone else not able to access it?

    Comments

    Tue, 10/13/2009 - 18:27 — rdprice29

    Nope. I just tried and it

    Nope. I just tried and it said "fatal mysql error" or somesuch. o_O

    Tue, 10/13/2009 - 19:40 — Sovran
    Sovran's picture

    Sigh

    Sadly, I'm the tech admin right now and I have no idea what the error message actually indicates.

    Tue, 10/13/2009 - 20:00 — parakletos
    parakletos's picture

    Sovran wrote: Sadly, I'm

    Sovran wrote:

    Sadly, I'm the tech admin right now and I have no idea what the error message actually indicates.

    Sounds like our tech support .....

    Tue, 10/13/2009 - 20:04 — Sovran
    Sovran's picture

    What can I say? I'm just a

    What can I say? I'm just a temp.

    Tue, 10/13/2009 - 20:37 — NotACat
    NotACat's picture

    The message I'm getting is:

    SIYE wrote:

    A fatal MySQL error was encountered.
    Query: SELECT * FROM fanfiction_categories WHERE parentcatid = '-1' ORDER BY displayorder
    Error: (2002) Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)

    This to me indicates that one of the following has happened:

    • MySQL has fallen over
    • The machine which is running MySQL has fallen over
    • The connection to the machine which is running MySQL is borked

    The latter two only apply if MySQL is running on a separate machine from the HTTP server, but I have no idea how the hosting arrangements of SIYE are arranged.

    I guess that basically what needs to happen is that somebody needs to prod one or more machines, and whether you can do this remotely is likewise beyond my knowledge. I only know that sometimes when Wikipedia glitches the only solution is for someone from the hosting company to manually reset various things.

    Tue, 10/13/2009 - 21:00 — parakletos
    parakletos's picture

    NotACat wrote: SIYE

    NotACat wrote:
    SIYE wrote:

    A fatal MySQL error was encountered.
    Query: SELECT * FROM fanfiction_categories WHERE parentcatid = '-1' ORDER BY displayorder
    Error: (2002) Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)

    This to me indicates that one of the following has happened:

    • MySQL has fallen over
    • The machine which is running MySQL has fallen over
    • The connection to the machine which is running MySQL is borked

    The latter two only apply if MySQL is running on a separate machine from the HTTP server, but I have no idea how the hosting arrangements of SIYE are arranged.

    I guess that basically what needs to happen is that somebody needs to prod one or more machines, and whether you can do this remotely is likewise beyond my knowledge. I only know that sometimes when Wikipedia glitches the only solution is for someone from the hosting company to manually reset various things.

    The error message mentions sock(s).... Ginny been stealing them again?

    Tue, 10/13/2009 - 21:12 — moshpit
    moshpit's picture

    Objectively speaking

    I don't formally know about the hosting company, but based on my informal "aid" to the various SIYE admins over time, I'm inclined to say the current ones have left me fairly unimpressed.

    For whatever reason, the replacement(s) post-admin-meltdown opted to move to the current host (and managed to thoroughly botch the move). A short period of time later, they stepped out of the picture, and Dino took over. Dino is more than competent to keep the show running, except he's still MIA on serious medical issues.

    Which leaves the remaining tech help staff. Meaning no offense to the current fill-in(s), the collective skill set is insufficient for doing anything more than keeping the site running with day to day routine tasks. Troubleshooting is not an option for this group.

    All of this leads to the amazingly simple conclusion that (a) SIYE needs to switch to a hosting company that's engaged fully and does this for a real job; and (b) they need to find a replacement for Dino post haste. One might suggest such conclusions are obvious and have been for a while, but I specialize in stating the obvious that no one else seems willing to.

    Key data for those that care:

    siye.co.uk. 3600 IN A 207.61.110.120
    siye.co.uk. 3600 IN NS toroondcnszs04.srvr.bell.ca.
    siye.co.uk. 3600 IN NS ns1.compar.com.
    siye.co.uk. 3600 IN SOA ns1.compar.com. noc.compar.com. 2008032101 10800 3600 604800 86400
    siye.co.uk. 3600 IN MX 20 mail4.compar.com.
    siye.co.uk. 3600 IN MX 10 mail3.compar.com.

    ns1.compar.com. 172748 IN A 216.208.38.130
    toroondcnszs04.srvr.bell.ca. 86348 IN A 207.236.176.22

    Registrant:
    HGnetworks

    Registrar:
    TUCOWS Inc [Tag = TUCOWS-CA]
    URL: http://www.opensrs.org

    Relevant dates:
    Registered on: 19-Mar-2006
    Renewal date: 19-Mar-2010

    Name servers:
    ns1.compar.com
    toroondcnszs04.srvr.bell.ca

    Tue, 10/13/2009 - 21:38 — TruckerRon

    Not as dead as a door nail...

    Yep, I'm just getting a bunch of warning messages...

    Warning: mysql_connect() [function.mysql-connect]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61) in /usr/local/www/data/www.siye.co.uk/siye/dbconfig.php on line 8

    Warning: mysql_select_db(): supplied argument is not a valid MySQL-Link resource in /usr/local/www/data/www.siye.co.uk/siye/dbconfig.php on line 9

    Tue, 10/13/2009 - 21:56 — Nifty_Niffler

    What a relief

    I'm so glad I'm not the only one experiencing this problem. I had just updated a story (I'm hgromance there) and realized I needed to do a bit of editing and suddenly I couldn't load the site anymore. I was beginning to worry that it was my own system. Hope it gets back up and running again soon.

    Wed, 10/14/2009 - 02:30 — Darkarma
    Darkarma's picture

    Ooooooooooooo time to check

    Ooooooooooooo time to check MinstryMalconent for new updates....

    Quote:

    A fatal MySQL error was encountered.
    Query: SELECT * FROM fanfiction_categories WHERE parentcatid = '-1' ORDER BY displayorder
    Error: (2002) Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)

    Damn you.... Damn you all to hell! You finally did it! You blew it up!

    ...

    From the error messages listed already looks like mine might be slightly different unless I missed something

    ...

    Lets just pretend that it is different data from what you seen. *Hides underneath a curtain*

    Wed, 10/14/2009 - 04:24 — Kezzabear

    Had MinistryMalcontent

    Had MinistryMalcontent updated with chapter 14?

    Wed, 10/14/2009 - 05:32 — NotACat
    NotACat's picture

    No worries about different messages

    Darkarma wrote:

    From the error messages listed already looks like mine might be slightly different unless I missed something

    The error messages would correspond to whatever the given page was requesting from the database. So some pages would have just a single error whereas some would have several. This also depends upon whether the given page gives up after getting an error or plugs on trying for more data.

    Wed, 10/14/2009 - 05:40 — moshpit
    moshpit's picture

    After much poking and prodding . . .

    . . . and other things that shall not be mentioned, I've confirmed the ISP's database server died.

    Apparently, the high quality standards have them just hopping to fix the problem. Someday. When they bother to check their problem logs. Or read their email. Or come back from vacation.

    Wed, 10/14/2009 - 14:37 — Sovran
    Sovran's picture

    SIYE is up

    The site is back up now. As several people (myself not included) realised, the server had to be rebooted.

    Wed, 10/14/2009 - 17:11 — Darkarma
    Darkarma's picture

    Kezzabear wrote: Had

    Kezzabear wrote:

    Had MinistryMalcontent updated with chapter 14?

    If only it twer, it would be twerrific! ~The previous quote, Planet of the Apes, this one Robin Hood Men Tights

    And finally yes SIYE seems to work... but no updates!

    *Flails around roaring...*

    Wed, 10/14/2009 - 19:04 — omega13b
    omega13b's picture

    From the looks of the error

    From the looks of the error message, I doubt the whole sever needed to be rebooted but whatever works. If those commands I sent in a private message didn't work and given the fact that a reboot solved the problem, then SIYE's server is configured in a really, really, weird way...

    A fish without a bicycle cannot contemplate his navel