I’m interested in too! We’re planning to move at the end of March, it would be great to move immediately to COS7. I would be satisfied with a good RC version 
Hi justec and dss
How long is a price of string…
It’s in pre beta but there’s obviously still issues, which are to be expected, which I’m sure will be in progress at development level.
I’m thinking a couple of months would mean a lot of dev work/beta testing, so I would be optimistic for justec time frame, match maybe a little too soon but hey, I could be wrong.
To be honest though, I would not expect an answer from IW unless it’s imminent perhaps.
I hope you don’t mind my thoughts as I could be entirely wrong
Many thanks
John
Thanks for the thoughts John.
I was asking because I have no idea what the project involves. I don’t know if they are adding in new InterWorx features and stuff or basically just testing the latest stable InterWorx release against CentOS and basically finding compatibility bugs and applying fixes.
That’s why I was just trying to get an official thought as far as most likely by June or most likely later.
Because I wouldn’t want to wait until November of this year, but I could make it a few more months because it will help me out in the long run.
Hey all! CentOS 7 support has been my main focus for the past six months. It presents a number of issues, such as the move to systemd, Apache 2.4, mariadb, firewalld, and a whole host of interesting service quirks (Apparently trying to enable debugging in systemd makes things unbootable. Who knew?). Most of the more serious issues (including some of those you guys found last week) have been ironed out to the point that things are relatively stable, and the current build is currently passing the vast majority of tests.
That said, a full CentOS 7 release relies on some other big features we’ve had coming down the line for a large part of 2014 – Nginx and Percona. These are the biggest parts of the forthcoming 5.1.0 release, and they’re closer than they’ve ever been, but I wouldn’t expect to see full CentOS 7 support until that version is released. As to how far off that is, I can’t really speculate (but a beta should be coming sooner rather than later).
Most importantly, all the feedback from this thread via support system has been enormously helpful in tracking and fixing bugs, making that the best method for contributing to the improvement of this project.
Keep up the great work, and I’ll be around to field any more questions.
Hi Matt,
Thank you for the information! I don’t know if there was any connection between systemd and virus filtering but I can’t start ClamAV and Freshclam. Or is stopped Freshclam “false offline” because it looks like the daily database is up to date.
Do you know when will be the next alpha version released?
Thanks for the heads-up Matt, looking forward to see nginx and percona support in Interworx! I would like to know, like dss, if the next alpha patch is coming soon? Will following problem be addressed?
2015-01-11 06:09:59.35278 [nosess-symc-460i-CLI] [EMERG] : ERROR: /usr/local/interworx/include/IWorxDbUtil.php(96): 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 : ip.php
2015-01-11 06:09:59.35301 [nosess-symc-460i-CLI] [EMERG] : : ip.php
2015-01-11 06:09:59.35325 [nosess-symc-460i-CLI] [EMERG] : #0 /usr/local/interworx/include/IWorxDbUtil.php(135): IWorxDbUtil::db_connect(‘mysql://iworx:I…’) : ip.php
2015-01-11 06:09:59.35342 [nosess-symc-460i-CLI] [EMERG] : #1 /usr/local/interworx/include/IW.php(143): IWorxDbUtil::getIWorxDBInstance() : ip.php
2015-01-11 06:09:59.35359 [nosess-symc-460i-CLI] [EMERG] : #2 /usr/local/interworx/include/IW.php(155): IW::DB() : ip.php
2015-01-11 06:09:59.35376 [nosess-symc-460i-CLI] [EMERG] : #3 /usr/local/interworx/include/IWorx/IP.php(1933): IW::localDB() : ip.php
2015-01-11 06:09:59.35393 [nosess-symc-460i-CLI] [EMERG] : #4 /usr/local/interworx/include/IWorx/IP.php(210): IWorx_IP::getDb() : ip.php
2015-01-11 06:09:59.35413 [nosess-symc-460i-CLI] [EMERG] : #5 /usr/local/interworx/include/IWorx/IP.php(734): IWorx_IP::factoryFromSearchEngine(Array, true) : ip.php
2015-01-11 06:09:59.35429 [nosess-symc-460i-CLI] [EMERG] : #6 /usr/local/interworx/include/IWorx/IP.php(1520): IWorx_IP::getIPObjects() : ip.php
2015-01-11 06:09:59.35445 [nosess-symc-460i-CLI] [EMERG] : #7 /usr/local/interworx/bin/ip.php(118): IWorx_IP::activateAll() : ip.php
2015-01-11 06:09:59.35462 [nosess-symc-460i-CLI] [EMERG] : #8 /usr/local/interworx/bin/ip.php(70): ip_setopts(Array) : ip.php
2015-01-11 06:09:59.35477 [nosess-symc-460i-CLI] [EMERG] : #9 /usr/local/interworx/bin/ip.php(54): ip(Array) : ip.php
2015-01-11 06:09:59.35493 [nosess-symc-460i-CLI] [EMERG] : #10 {main} : ip.php
2015-01-11 06:09:59.35578 [nosess-symc-460i-CLI] [EMERG] : ----- DEBUG STACKTRACE BEGIN ----- : ip.php
2015-01-11 06:09:59.35599 [nosess-symc-460i-CLI] [EMERG] : /usr/local/interworx/include/IWorxDebug.php getStackTrace (167) : ip.php
2015-01-11 06:09:59.35620 [nosess-symc-460i-CLI] [EMERG] : 0 exceptionHandler (0) : ip.php
2015-01-11 06:09:59.35640 [nosess-symc-460i-CLI] [EMERG] : ----- DEBUG STACKTRACE END ----- : ip.php
Cheers, glenkinchie
[QUOTE=IWorx-Matt;26884]Hey all! CentOS 7 support has been my main focus for the past six months. It presents a number of issues, such as the move to systemd, Apache 2.4, mariadb, firewalld, and a whole host of interesting service quirks (Apparently trying to enable debugging in systemd makes things unbootable. Who knew?). Most of the more serious issues (including some of those you guys found last week) have been ironed out to the point that things are relatively stable, and the current build is currently passing the vast majority of tests.
That said, a full CentOS 7 release relies on some other big features we’ve had coming down the line for a large part of 2014 – Nginx and Percona. These are the biggest parts of the forthcoming 5.1.0 release, and they’re closer than they’ve ever been, but I wouldn’t expect to see full CentOS 7 support until that version is released. As to how far off that is, I can’t really speculate (but a beta should be coming sooner rather than later).
Most importantly, all the feedback from this thread via support system has been enormously helpful in tracking and fixing bugs, making that the best method for contributing to the improvement of this project.
Keep up the great work, and I’ll be around to field any more questions.[/QUOTE]
Couldn’t be here if it wasn’t for you guys working so hard on the best control panel ever 
so Thank you Matt mate for your hard work. Roll on beta 
Hi
Excellent news on centos 7, I’m looking forward to IW 5.1, but more importantly, it gives me more time to set aside a test server and burn a centos7 DVD. Perconna and ngix should make a bug difference, certainly to loading on server.
Dss, I think clamav is slightly different on the latest version, and freshclam is not used, do you have l or v, ie .cld or .cvd. If so, one is compressed and one is not compressed, and updates are differential, but you should not have both. This I think is why it shows as updated, but I’ll need to reread some clam emails again, sorry, memory fading.
Many thanks
John
Is there any closer time when the next build will be available? I’m planning to reinstall a VPS on Sunday, it would be great to use Centos 7. It’s only a DNS and backup server so I can use alpha/beta release if DNS sync works.
Definitely not by this Sunday The next build of CentOS7 support will be included in the the 5.1 rollout when that happens. At this point we don’t have a public timetable for that release, but it’s definitely in the short term.
A visibility for an announcement ?
Hi guys!
I’m setting up a new server and I want to ask if its ok using Centos7 with your latest version. On that server I will only have 2 sites but I’m looking to import more of them down the road.
Hi onspot
I personally would not want to use centos 7 IW until it moves into production state, from beta.
I’m sure as Brett posted, it should not be long, but I understand your probably posting for IW to respond, but unless the release is ready, I do not think they will give any time frames.
I hope you do not mind my thoughts
Many thanks
John
Thanks for the reply John, I really appreciate it
I just decided to move into a CentOS 6 server, tried to wait it out but now can wait for any little CentOS 7 / Iworx production bugs to be worked out before I move over.
Found the following bugs (On CentOS 7 x86_64 OpenVZ, IPv6 enabled):
Can’t login on RoundCube webmail.
Squirrelmail and horde both work.
The error log shows:
[31-Mar-2015 14:35:22 -0400]: DB Error: [1364] Field 'alias' doesn't have a default value (SQL Query: INSERT INTO users (created, last_login, username, mail_host, language) VALUES (now(), now(), 'admin@site.nl', 'localhost', 'nl_NL')) in /usr/local/interworx/lib/roundcube/program/lib/Roundcube/rcube_db.php on line 466 (POST /roundcube/?_task=login?_task=login&_action=login)[31-Mar-2015 14:35:22 -0400]: PHP Error: Failed to create new user in /usr/local/interworx/lib/roundcube/program/lib/Roundcube/rcube_user.php on line 584 (POST /roundcube/?_task=login?_task=login&_action=login)
[31-Mar-2015 14:35:22 -0400]: PHP Error: Failed to create a user record. Maybe aborted by a plugin? in /usr/local/interworx/lib/roundcube/program/include/rcmail.php on line 610 (POST /roundcube/?_task=login?_task=login&_action=login)
Sites give an forbidden waring, this is the solution, edit the vhost file and add "Require all granted":
<Directory /home/sitenl/site.nl/html>
AllowOverride All
Require all granted
</Directory>
Nodeworx is displaying the error “Warning, mod_php and mod_suphp are both enabled, this is a security risk!”
This is right. You can disable mod_php5 by doing this in the shell:
mv /etc/httpd/conf.modules.d/10-php.conf /etc/httpd/conf.modules.d/10-php.conf.disabled
touch /etc/httpd/conf.modules.d/10-php.conf
The server-status and server-info page do not work after adding the required config lines to httpd.conf:
ExtendedStatus On
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Location>
<Location /server-info>
SetHandler server-info
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Location>
Changing “127.0.0.1” to localhost solves this problem.
Apache modules are not displayed in the InterWorx webserver service menu, but they are installed. (You can check this with server status)
The webserver doesn’t restart after clicking save & restart after editing httpd.conf
Restarting in NodeWorx also doesn’t work, you have to do this manualy via the shell.
MySQL/MariaDB didn’t want to start, seems it can’t read the /etc/my.cnf.d directory, so uncommented it in /etc/my.cnf, because there is no configuration in these files:
#!includedir /etc/my.cnf.d
Restart and status is OK now:
# systemctl restart mariadb.service
# systemctl status mariadb.service
mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled)
Active: active (running) since Tue 2015-03-31 21:05:48 CEST; 7s ago
Process: 20772 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
Process: 20742 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 20771 (mysqld_safe)
CGroup: /system.slice/mariadb.service
??20771 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
??21071 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-fi...
Mar 31 21:05:47 v1.unusual-ict.nl mysqld_safe[20771]: 150331 21:05:47 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Mar 31 21:05:47 v1.unusual-ict.nl mysqld_safe[20771]: 150331 21:05:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
That’s it for now
Got this problem after playing arround a bit with everything working fine for a couple of days after logging in:
System Error
A system error has occurred. Please try your request again in a few minutes.
If the problem persists, please contact Support.
this is from the iworx log:
2015-04-08 19:22:03.95255 [nosess-g6o5-kst7-WEB] [INFO] : 1.2.3.4 routing: Ctrl_Nodeworx_Index -> index : /nodeworx/
2015-04-08 19:22:23.37096 [nosess-5luu-48d7-WEB] [INFO] : 1.2.3.4 routing: Ctrl_Nodeworx_Index -> login : /nodeworx/?action=login
2015-04-08 19:22:23.45155 [nosess-5luu-48d7-WEB] [INFO] : 1.2.3.4 routing: Ctrl_Nodeworx_Index -> loginCommit : /nodeworx/?action=login
2015-04-08 19:22:24.54824 [vlb35m-1dy1-z6gk-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-04-08 19:22:24.54845 [vlb35m-1dy1-z6gk-WEB] [EMERG] : ----- DEBUG STACKTRACE BEGIN ----- : /nodeworx/overview
2015-04-08 19:22:24.54852 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/IWorxDebug.php getStackTrace (167) : /nodeworx/overview
2015-04-08 19:22:24.54860 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/IWorxDebug.php errorHandler (87) : /nodeworx/overview
2015-04-08 19:22:24.54867 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/syslog.php debug_assert (72) : /nodeworx/overview
2015-04-08 19:22:24.54873 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/syslog.php GPGWrapper (401) : /nodeworx/overview
2015-04-08 19:22:24.54880 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/License.php IWorxGPG (60) : /nodeworx/overview
2015-04-08 19:22:24.54886 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/License.php __construct (83) : /nodeworx/overview
2015-04-08 19:22:24.54892 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/IW.php getInstance (197) : /nodeworx/overview
2015-04-08 19:22:24.54898 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/cluster/NodeManager.php License (110) : /nodeworx/overview
2015-04-08 19:22:24.54904 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/nodeworx/NodeWorx.php canCluster (919) : /nodeworx/overview
2015-04-08 19:22:24.54912 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/View/Smarty/Nodeworx.php getSmarty (45) : /nodeworx/overview
2015-04-08 19:22:24.54918 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/Env/HTML.php __construct (209) : /nodeworx/overview
2015-04-08 19:22:24.54924 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/Ctrl/Abstract.php initView (65) : /nodeworx/overview
2015-04-08 19:22:24.54930 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/Ctrl/Nodeworx/Abstract.php __construct (45) : /nodeworx/overview
2015-04-08 19:22:24.54936 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/FrontController.php __construct (345) : /nodeworx/overview
2015-04-08 19:22:24.54942 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/FrontController.php _invokeAction (147) : /nodeworx/overview
2015-04-08 19:22:24.54948 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/include/FrontController.php _route (96) : /nodeworx/overview
2015-04-08 19:22:24.54954 [vlb35m-1dy1-z6gk-WEB] [EMERG] : /usr/local/interworx/html/index.php route (37) : /nodeworx/overview
2015-04-08 19:22:24.54960 [vlb35m-1dy1-z6gk-WEB] [EMERG] : ----- DEBUG STACKTRACE END ----- : /nodeworx/overview
EDIT:
Running cvspermsfix.pex fixed the problem
I am going to install Interworx on CentOS 7 and started reading the instructions. I looked at http://www.interworx.com/support/faq/enabling-quotas-centos7 on how to enable quotas. It says to save a copy of grub at /boot/grub2/grub.cfg. That sounds good, but on my new install, it’s not there. I did find grub at /boot/efi/EFI/centos/grub.cfg. Is this the correct grub I want to save?
Thanks!
Hi bummer
I believe your correct in grub, as Efi I think is just a boot loader I believe.
Please be aware though, which I’m sure you know, but centos 7 IW is in beta and should not be used in production servers. Well, that’s my advice anyway.
Good luck and I’d appreciate if you update your post after you’ve installed it
Many thanks
John
Hey John,
I know IW is in beta, I’m chomping at the bit to use it on CentOS 7. But I want to play with it now and do some testing. As you can see, I already had a question and I haven’t even started to install IW yet!