Skip to main content

EasyApache Build Stuck On "-- Begin 'Mod Security' is off--"

Comments

7 comments

  • cPanelNick
    Please open a ticket using the link in my signature
    0
  • maxija
    Ok will do that now.
    0
  • esa
    I have the same issue life now. Centos 6.4 32Bit with the following additions/selections PHP Encryption and Image Manipulation Apache 2.4.6 php 5.4.20 disable frontpage Curl Mbstring MySQL "Improved" extension
    0
  • cPanelMichael
    Hello :) To update, ticket numbers 4358019 and 4358105 were opened by the posters on this thread reporting the problem. The issue was resolved by running EasyApache via the command line, but an exact cause of the issue was not found. Anyone else experiencing this issue should open a support ticket and request the issue is reproduced using WHM (assuming the problem is isolated to WHM). Remember to provide the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • jimlongo
    I have 3 VPS's with 2 different providers. On 2 of the servers (2 different providers) last night I did not recieve the usual upcp email notice. So I tried to run easyApache via WHM on those 2 servers. Both got stuck at the same point. Both were able to be completed with the commandline /scripts/easyapache /opt/php_with_imap_client//lib/libc-client.a(osdep.o): In function `ssl_onceonlyinit': /home/cpeasyapache/src/imap-2007f/c-client/osdep.c:302: warning: the use of `tmpnam' is dangerous, better use `mkstemp' Generating phar.php Generating phar.phar /opt/php_with_imap_client//lib/libc-client.a(osdep.o): In function `ssl_onceonlyinit': /home/cpeasyapache/src/imap-2007f/c-client/osdep.c:302: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
    I've opened ticket #4366785 in regards to one server
    0
  • jimlongo
    This ticket has been closed with no definitive causation. Seems to possibly be an issue with EA not exiting cleanly and continuing to run, maybe something to do with 11.40.06 upcp update.
    0
  • Brian
    Howdy, I just wanted to send a quick update here. I performed a further in-depth look into jimlongo's server. I've been unable any culprits thus far. The upcp cron seems to have run correctly in this case and, in the case of jimlongo's server specifically, the EasyApache build itself may have hung up on a particular "pear" command. It's unclear at this time since I am having to approach it from a "post-resolution" standpoint. The pear command does not hang or have any issues at all when run manually after the fact. I encourage anyone else experiencing a similar issue to leave EasyApache and/or upcp in its problematic state and open a ticket immediately. It would be extremely advantageous to see the state of things while the problem is active. This should help us identify what, if anything, is faulting in the process. Thus far I haven't been able to pin down any bugs. As mentioned, whenever we try to reproduce it, the build seems to go through flawlessly. Please cite this thread specifically when opening a ticket about this. Thanks.
    0

Please sign in to leave a comment.