Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 3953 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

error: %post(savinstpkg-0.0-1.i386) scriptlet failed, exit status 1

cmschube

That's the error I get when trying to run the install package on a Centos 5.5 x86 box. When I run the install.sh manually, I get the following:

[root@labcentos tmp]# /tmp/sophos-av/install.sh
Downloading labepo/.../server.inf
Downloading labepo/.../server.inf
Downloading labepo/.../cidsync.upd
Downloading labepo/.../cidsync.upd
Downloading labepo/.../master.upd
Can't locate index of labepo/.../savlinux
Failed to replicate from labepo/.../savlinux
Failed to replicate from all update sources
[root@labcentos tmp]#

I can't figure out what I'm doing wrong here.

I saw a post that say something about the "double escape" on IIS 7 and I did disable that and restarted the website and IIS all together, but I'm having the same problem.

Any help is appreciated-

Chris

:5589


This thread was automatically locked due to age.
  • 0

    Hello Chris,

    IIS can be tricky. Check the IIS logs (wherever they are) and try to locate the last request from the client (might be it requests the index of /savlinux). Enter the request in a browser (preferably from Centos). If you don't get the expected content or directory listing then some IIS setting is the culprit (it could, for example., do some server-side processing for certain extensions instead of simply serving the file's contents)

    Christian

    :5590
  • 0

    Hey Christian -

    Thanks for the ideas. Just as a follow up (I hate it when people post something a question and then post the end resolution). I fixed the issue by adding a .* mime type entry into IIS for the website. (text/plain).

    Hope this helps out someone at some point.

    Chris

    :5615
  • 0

    Hello Chris,

    fine you've solved it.

    Two remarks though:

    1. I suggest application/octet-stream for the catch-all entry for obvious reasons
    2. Make sure no other definitions are in effect for the website.  Depending on the "features" installed on Windows special processing might be triggered for certain extensions (it is possible that IIS' behaviour changes after a Window update ...)   

    Christian

    :5625
Unfiltered HTML