one fail on first build inifpsuexec

durangod

• July 20, 2014 13:52

Hi, Installing to new VPS i got this one fail, was wondering if it was anything to be concerned about. [QUOTE] Executing '/scripts/initfpsuexec' !! !! '/scripts/initfpsuexec' failed with exit code '256' !!
it did finish, i did not know it finished, it did not say so in the box, but after a while i hit refresh output box and then it showed completed. so is this anything i need to worry about... thanks :)

• 

  vanessa

  • July 20, 2014 22:10

  What happens when you try to run /scripts/initfpsuexec?

  0
• 

  durangod

  • July 20, 2014 23:07

  from the root command line or from url ? from url - if i did this right because i dont have my cert installed yet, i get a blank page maybe i should try to force it should i try something like this from command line /scripts/initfpsuexec --force
  im new at this so im just guessing at that syntax or process

  0
• 

  vanessa

  • July 20, 2014 23:35

  Based on what you pasted originally, there was implication that the problem was the script. Perhaps try building again and see if it happens again.

  0
• 

  durangod

  • July 20, 2014 23:42

  would you happen to know what exit code 256 is? i did google it and found this if i can manage to reason this out for 256 lol [QUOTE] Exit codes are a number between 0 and 255, which is returned by any Unix command when it returns control to its parent process. Other numbers can be used, but these are treated modulo 256, so exit -10 is equivalent to exit 246, and exit 257 is equivalent to exit 1.
  I also dont see a rebuild option in WHM if i wanted to try that how would i do that. All i see is apache config page and it does not rebuild it just updates right?

  0
• 

  vanessa

  • July 20, 2014 23:54

  256 is not a standard exit code, but programs can define their own. EA just uses it as a generic exit code for failures.

  0
• 

  durangod

  • July 21, 2014 00:00

  that file is a frontpage script, im wondering if since i am just now setting up the VPS, my first time ever. If maybe (and this is just a stab in the dark here) should have turn on or configured frontpage first and then apache, maybe that is the issue. If that is how it works, or is frontpage a part of apache i dont know. But that would make sense to me. I dont plan on using frontpage anyway and i dont imagine any of my clients will. If there is a way to just turn off frontpage from config then if youll tell me how to do that ill do that lol.. and then we can call this one done lol

  0
• 

  vanessa

  • July 21, 2014 00:01

  Frontpage isn't supported in EA anymore, unless you specifically installed the module for it. [url=http://cpanel.net/end-of-the-road-for-frontpage-installations-what-to-expect/]End of the Road for FrontPage Installations: What to Expect | cPanel, Inc.

  0
• 

  durangod

  • July 21, 2014 00:04

  thank you mam that certainly fries that chicken dont it lol... had a good day :)

  0
• 

  estrabd

  • July 21, 2014 12:59

  [quote="vanessa, post: 1690791">256 is not a standard exit code, but programs can define their own. EA just uses it as a generic exit code for failures.
  FWIW, 256 is the exit code associated with Perl's "die" method; which would make a lot of sense here.

  0
• 

  cPanelMichael

  • July 21, 2014 17:44

  Hello :) Please keep in mind that you are welcome to open a complimentary support ticket if the issue persists. You could then post the ticket number here and we can update this thread with the outcome. Thank you.

  0
• 

  KurtN.

  • July 23, 2014 20:08

  The exit 256 output is a known issue, and is currently being worked on as apart of a larger project. This issue does not cause EasyApache to fail to build and can be safely ignored until resolved.

  0

Please sign in to leave a comment.