Announcement

Collapse
No announcement yet.

Apache and .fil

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Apache and .fil

    Apologies if someone points me to an existing thread, I searched but the two I found didn't seem relevant.

    I posted before after a server move and managed to get Sellerdeck working with a perl script edit from support.

    After a hardware failure we were moved to a new server (Dedicated but unmanaged) SD wouldn't upload/run.

    After many conversations with SD support they (rightly) said there wasn't much they could do as by this time both they and I had tried it on different servers from the problem one and the settings/contents were fine on both.

    The guys I rent the server from and who moved the files from the failed hard-drive say their responsibility stops at providing a server that runs. (although nothing ran on it after the transfer)

    The server support I use don't know anything about SD and say it could be a missing plesk module but which one. (they have spent days trying to get it to work.)

    1) I was getting a permissions error but we seem to have solved that as Ascii support was switched off. - now on
    2) I get an error saying the servers scripts are incompatible with this version of SD - I have deleted/refreshed and purged and refreshed as well as buying Access to delete the file list all to no avail.
    3) I get a message that old***.fil files have been edited when publishing site or trying to download orders - this seems to be because apache keeps taking ownership of them - The server guys change it back to me and then it changes again.
    4)I get a failed to merge error at the end of publishing but think this is to do with the .fil error.

    Does any one have any idea what I am missing? Thanks in advance for any suggestions.

    #2
    I get an error saying the servers scripts are incompatible with this version of SD
    This one sounds like you should check what version of PERL you have running and whether it is compatible with sellerdeck.

    I get a message that old***.fil files have been edited when publishing site or trying to download orders - this seems to be because apache keeps taking ownership of them
    This sounds like it could be a permissions setting. Anything other than basic permissions settings are beyond me I'm afraid. I assume you've set permissions to the standard 755.
    -----------------------------------------

    First Tackle - Fly Fishing and Game Angling

    -----------------------------------------

    Comment


      #3
      Hi Mike, thanks for posting. :-)

      I will ask them to check the perl version the actual error shows the two versions but oone has no numbers only commas and letters and the other shows the proper version.

      They set the permissions as 777 on the actinic folder and 755 on the cgi-bin. I'm not sure why apache keeps resetting ownership though.

      I'll let you know about the perl version. Is it worth reinstalling it, could it get corrupted during a move?

      Comment


        #4
        Hi Andy,

        i'm afraid this is where my server knowledge runs out.

        Unmanaged Dedicated servers have always been a bit of a specialist area and one I've avoided.

        AFAIK there can be various security mods running on servers that can over-ride the standard file permissions settings.

        I wouldn't expect a simple hardware move to affect things much but I have no idea if the servers would be identical in terms of setup or not.
        -----------------------------------------

        First Tackle - Fly Fishing and Game Angling

        -----------------------------------------

        Comment


          #5
          Thanks Mike, I await an update from the server guys.

          Comment


            #6
            Well that will be that then?

            "Not sure regarding why apache is doing so as the we dont know on what point apache is triggered to write on the file.
            I dont think its due to a corrupted perl. I have checked the perl binary and we are using perl 5.16 in the server and a test perl script worked fine for me."

            Comment


              #7
              Just to update incase anyone searches and finds this thread, hopefully it will save them some time and tears.

              It seems to have been something to do with Plesk, we unfortunatley were unable to find exactly what the error was but the site is now running fine on a new server under Cpanel.

              Comment

              Working...
              X