CentOS 7 Suppport now in Pre-Beta!

Many of you have been asking for it, and now you can try it for yourself – InterWorx can now by installed on CentOS 7!

Please bear in mind that this is a pre-beta, so we don’t recommend using for production purposes yet.

To install InterWorx on CentOS7:

[LIST=1]

  • Do a fresh install of CentOS 7 minumum (http://www.centos.org/download/). Upgrading from CentOS6 is NOT recommended.
  • If you're using XFS (default), enable Quotas (optional, but recommended. See here for instructions)
  • Run the CentOS7 install script:
    sh <((curl -sL interworx.com/inst.sh)) -r beta
    

    [/LIST]
    Enjoy! If you run into any issues while testing InterWorx on CentOS7, let us know at support@interworx.com!

  • Hi Brett,

    I tried to do a quick test on a DO droplet, but I can’t install IW. I always get the following message.

    STATUS: Determining Linux distribution
    ERROR: CentOS Linux release 7.0.1406 (Core)  not supported, override with -f
    tail: cannot open ?iworx-install.log? for reading: No such file or directory
    
    

    I created the iworx-install.log file manually, but the error occurs again, OS not supported. The installed OS is: CentOS Linux release 7.0.1406 (Core)

    I checked the iworx-cp-install.sh file and it does not contains anything about Centos 7. Is it the correct file?

    Hey DSS – try it now!

    Working for me at the moment.

    Much better, installing :slight_smile:

    Installed succesfull, but can’t activate:

    [STATUS] Go! InterWorx
     [STATUS] License Key Setup...
     [STATUS] Validating license information... 
     [STATUS] Setting up PHP-CGI...
     [STATUS] Setting up initial InterWorx Databases...
     [WARNING] Looks like iworx was setup before on this box...
     [WARNING] Problem setting up DB info. Trying again...
     [STATUS] Setting up initial InterWorx Databases...
     [WARNING] Looks like iworx was setup before on this box...
     [ERROR] Database setup failed. Please contact InterWorx Support.
     [ERROR] Activation Failed
    

    Hey dss – can you email support@interworx.com about that? We’ll need to get access to the machine to see what’s going on there.

    We didn’t have enough free memory. It was a small VPS with 512MB of RAM. I tried to activate with ~300MB of free RAM, but it wasn’t enough too. I’m going to install this version on a different (bigger) VPS in mid-Januray.

    The older versions with CentOS 5/6 wokrs fine with 512MB of RAM.

    Happy New Year!

    going to try this on a centos7 server, anyone else had success getting it working ok
    has any one had any other issues

    I could install Interworx successfully on a Centos 7 test server. I noticed 3 things so far:

    1. In the activation script the step “Setting up Roundcube DB” throws an error: ERROR 1091 (42000) at line 225: Can’t DROP ‘uid’; check that column/key exists
    2. After the fresh setup, mod_php and mod_suphp are both enabled: “Warning, mod_php and mod_suphp are both enabled, this is a security risk!”
    3. No apache modules are shown: “No records matched your search”

    I can confirm the 2nd and 3rd! I noticed, that I can’t change SSH port, and can’t set up DNS synchronization.

    It would be good to make a public or a private (with invited users) bug tracker to collect the possible bugs, it’s much easier then send support tickets 2-3 times about a problem.

    glenkinchie: Did you discover any problem with the homepages? I had to modify the config files to be able to open the default SiteWorx page.

    I had a quick look at the DNS synchronization, I get an error too: ? Error adding DNS host : xxx.xxx.xxx.xx => hostname.domain.tld. Test completes with success. I can’t tell you if changing SSH Port is working, I changed mine before running the Interworx script. I didn’t add a domain yet, so I can’t really say if the homepages are working. But I can imaginge that the problems results of the two acitvated mods php and suphp.

    [QUOTE=glenkinchie;26812]I could install Interworx successfully on a Centos 7 test server. I noticed 3 things so far:

    1. In the activation script the step “Setting up Roundcube DB” throws an error: ERROR 1091 (42000) at line 225: Can’t DROP ‘uid’; check that column/key exists
    2. After the fresh setup, mod_php and mod_suphp are both enabled: “Warning, mod_php and mod_suphp are both enabled, this is a security risk!”
    3. No apache modules are shown: “No records matched your search”[/QUOTE]

    Hey guys! Great feedback so far! I’m working on the apache stuff now (so much changed from 2.2 to 2.4).

    I believe #1 is unrelated to the CentOS 7 changes, but I’ve made a note of it.

    With regards to #2, this is due to some web server configuration files being split out. Near as I can tell, the ‘security risk’ error is a false positive and can be suppressed by commenting out the contents of /etc/httpd/conf.modules.d/10-php.conf. This will prevent mod_php from attempting to load automatically and allow InterWorx to handle things. I should have a more appropriate fix for this one soon.

    I’m also looking into #3 now. Thanks again!

    Hi Matt,

    Thank you for your feedback. My installation totally died tomorrow, I can’t login. What can I do?

    This is what I can see when opening NodeWorx:

    And the SSH output:

    [root@srv4 ~]# /bin/systemctl status  iworx.serviceiworx.service - SYSV: InterWorx
       Loaded: loaded (/etc/rc.d/init.d/iworx)
       Active: [B]active (running)[/B] since h 2015-01-05 07:52:25 CET; 7h ago
      Process: 31024 ExecStop=/etc/rc.d/init.d/iworx stop (code=exited, status=0/SUCCESS)
      Process: 31041 ExecStart=/etc/rc.d/init.d/iworx start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/iworx.service
               ├─31044 /bin/sh /home/interworx/mysql/usr/bin/mysqld_safe --defaults-file=/home/interworx/mysql/my.cnf
               ├─31078 /home/interworx/bin/iworx-web -f /home/interworx/etc/httpd/httpd.conf -DSSL
               ├─31667 /home/interworx/mysql/usr/sbin/iworx-db-2 --defaults-file=/home/interworx/mysql/my.cnf --basedir=/home/interworx/mysql --datadir=/home/interworx/mysql/data --plugin...
               ├─31915 /home/interworx/bin/iworx-web -f /home/interworx/etc/httpd/httpd.conf -DSSL
               └─31916 /home/interworx/bin/iworx-web -f /home/interworx/etc/httpd/httpd.conf -DSSL
    
    
    jan 05 07:52:25 srv4.host.com iworx[31041]: #7 /usr/local/interworx/bin/ip.php(118): IWorx_IP::activateAll()
    jan 05 07:52:25 srv4.host.com iworx[31041]: #8 /usr/local/interworx/bin/ip.php(70): ip_setopts(Array)
    jan 05 07:52:25 srv4.host.com iworx[31041]: #9 /usr/local/interworx/bin/ip.php(54): ip(Array)
    jan 05 07:52:25 srv4.host.com iworx[31041]: #10 {main}
    jan 05 07:52:25 srv4.host.com iworx[31041]: ----------------------------------------------------------------
    jan 05 07:52:25 srv4.host.com iworx[31041]: ----- DEBUG STACKTRACE BEGIN -----
    jan 05 07:52:25 srv4.host.com iworx[31041]: 0 exceptionHandler (0)
    jan 05 07:52:25 srv4.host.com iworx[31041]: ----- DEBUG STACKTRACE END   -----
    jan 05 07:52:25 srv4.host.com iworx[31041]: Binding IP Aliases:  [FAILED]
    jan 05 07:52:25 srv4.host.com systemd[1]: Started SYSV: InterWorx.
    

    iw_error.jpg

    Hi dss

    I think your error is on ip bindings, and I’ve seen this on centos 6…

    I have posted in forum how to clear it, as something has not released ip/port, but if you can’t find the post, just restart server and it should clear it.

    I could be wrong though, so apologies in advance, and sorry, I am very eager to try centos 7, but am not in a position to at the moment. I did try to install using USB stick, made via windows and hit the special folder which is not transferred correctly, so will have to wait, but I’m following this thread

    Hope that helps

    Many thanks

    John

    John, thank you for your reply! That was the first I tried but unfortunately not working.

    Thanks for the reply, Matt.

    Today I’ve got the same error as dss, the server died. When I login to Nodeworx I get following message:

    System Error
    A system error has occurred. Please try your request again in a few minutes.
    If the problem persists, please contact Support.

    After a reboot, the iworx service wasn’t running anymore. After a manual start I again get the same errors as dss (note that the timestamp of the log is also way off: server time is: 17.28h and log stamp is 11:28h)

    2015-01-05 11:28:51.52613 [m1c704-v8wk-0dci-WEB] [EMERG] : ERROR: /usr/local/interworx/include/syslog.php(72): ----- ASSERTION FAILED BEGIN -----<br>ASSERTION FAILED: /usr/local/interworx/include/syslog.php (72): <br>----- ASSERTION FAILED END -----<br> : /nodeworx/overview
    2015-01-05 11:28:51.52642 [m1c704-v8wk-0dci-WEB] [EMERG] : ----- DEBUG STACKTRACE BEGIN ----- : /nodeworx/overview
    2015-01-05 11:28:51.52652 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/IWorxDebug.php getStackTrace (167) : /nodeworx/overview
    2015-01-05 11:28:51.52661 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/IWorxDebug.php errorHandler (87) : /nodeworx/overview
    2015-01-05 11:28:51.52676 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/syslog.php debug_assert (72) : /nodeworx/overview
    2015-01-05 11:28:51.52690 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/syslog.php GPGWrapper (401) : /nodeworx/overview
    2015-01-05 11:28:51.52698 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/License.php IWorxGPG (60) : /nodeworx/overview
    2015-01-05 11:28:51.52706 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/License.php __construct (83) : /nodeworx/overview
    2015-01-05 11:28:51.52713 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/IW.php getInstance (197) : /nodeworx/overview
    2015-01-05 11:28:51.52721 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/cluster/NodeManager.php License (110) : /nodeworx/overview
    2015-01-05 11:28:51.52728 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/nodeworx/NodeWorx.php canCluster (919) : /nodeworx/overview
    2015-01-05 11:28:51.52736 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/View/Smarty/Nodeworx.php getSmarty (45) : /nodeworx/overview
    2015-01-05 11:28:51.52743 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/Env/HTML.php __construct (209) : /nodeworx/overview
    2015-01-05 11:28:51.52750 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/Ctrl/Abstract.php initView (65) : /nodeworx/overview
    2015-01-05 11:28:51.52757 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/Ctrl/Nodeworx/Abstract.php __construct (45) : /nodeworx/overview
    2015-01-05 11:28:51.52766 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/FrontController.php __construct (345) : /nodeworx/overview
    2015-01-05 11:28:51.52778 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/FrontController.php _invokeAction (147) : /nodeworx/overview
    2015-01-05 11:28:51.52786 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/include/FrontController.php _route (96) : /nodeworx/overview
    2015-01-05 11:28:51.52793 [m1c704-v8wk-0dci-WEB] [EMERG] : /usr/local/interworx/html/index.php route (37) : /nodeworx/overview
    2015-01-05 11:28:51.52805 [m1c704-v8wk-0dci-WEB] [EMERG] : ----- DEBUG STACKTRACE END ----- : /nodeworx/overview

    And I get an additional MySQL error:

    [root@juno ~]# systemctl status iworx -l
    iworx.service - SYSV: InterWorx
    Loaded: loaded (/etc/rc.d/init.d/iworx)
    Active: active (running) since Mon 2015-01-05 17:17:52 CET; 20min ago
    Process: 2280 ExecStart=/etc/rc.d/init.d/iworx start (code=exited, status=0/SUCCESS)
    CGroup: /system.slice/iworx.service
    ├─2282 /bin/sh /home/interworx/mysql/usr/bin/mysqld_safe --defaults-file=/home/interworx/mysql/my.cnf
    ├─2482 /home/interworx/bin/iworx-web -f /home/interworx/etc/httpd/httpd.conf -DSSL
    ├─2875 /home/interworx/mysql/usr/sbin/iworx-db-2 --defaults-file=/home/interworx/mysql/my.cnf --basedir=/home/interworx/mysql --datadir=/home/interworx/mysql/data --plugin-dir=/usr/lib64/mysql/plugin --user=iworx --log-error=/home/interworx/mysql/error.log --open-files-limit=65535 --pid-file=/home/interworx/mysql/iworx-db.pid --socket=/home/interworx/mysql/iworx-db.sock --port=2307
    ├─2951 /home/interworx/bin/iworx-web -f /home/interworx/etc/httpd/httpd.conf -DSSL
    └─3785 /home/interworx/bin/iworx-web -f /home/interworx/etc/httpd/httpd.conf -DSSL

    Jan 05 17:17:51 my.domain.tld systemd[1]: Starting SYSV: InterWorx…
    Jan 05 17:17:51 my.domain.tld iworx[2280]: Starting InterWorx-db: [ OK ]
    Jan 05 17:17:51 my.domain.tld iworx[2280]: Starting InterWorx-web: [ OK ]
    Jan 05 17:17:52 my.domain.tld iworx[2280]: Uncaught IWorx_Exception_DbUtil: DB Error: connect failed [nativecode=Can’t connect to local MySQL server through socket ‘/usr/local/interworx/mysql/iworx-db.sock’ (2)] ** mysql://iworx:fjt8wn1lkj@unix(/usr/local/interworx/mysql/iworx-db.sock)/iworx
    Jan 05 17:17:52 my.domain.tld iworx[2280]: A system error has occurred. Please try your request again in a few minutes.
    Jan 05 17:17:52 my.domain.tld iworx[2280]: If the error persists, please contact support.
    Jan 05 17:17:52 my.domain.tld iworx[2280]: Binding IP Aliases: [FAILED]
    Jan 05 17:17:52 my.domain.tld systemd[1]: Started SYSV: InterWorx.

    Hi dss

    Sorry, should have known you’d have tried restart sorry.

    Have you both opened a support ticket so IW could have a look to see what’s going on.

    Last thought, which I’m sure you’ve tried, if you completed matts suggestion over mod php, have you reversed it and restarted to see if it’s connected.

    Many thanks

    John

    [QUOTE=d2d4j;26827]Hi dss

    Sorry, should have known you’d have tried restart sorry.

    Have you both opened a support ticket so IW could have a look to see what’s going on.

    Last thought, which I’m sure you’ve tried, if you completed matts suggestion over mod php, have you reversed it and restarted to see if it’s connected.

    Many thanks

    John[/QUOTE]

    Unfortunately, not solved. Now I’m waiting for the support team. It’s only a test VPS so I have time :slight_smile: Thank you for your help!

    I’m sure there isn’t a good answer to this, but I’m going to ask anyway :stuck_out_tongue:

    Is there any ETA on a production version of IW with COS7 support? I’ve decided it’s time to upgrade my server, but since I’ve waited “this long” I’m debating just waiting it out more so I can move right to CentOS7. It’s such a pain in the butt moving because I always just get a new server with a fresh install of CentOS and then move all my sites over.

    If it’s likely to happen before June I’ll probably wait, if not I won’t.

    Thanks!