I tweeted InterWorx today to try and get some light into the Centos 7 5.1 version and they said (Don’t know who uses the account now Brett’s gone) that it is now in Release Candidate. i thought GREAT! Let’s try it…
Got the 5.1 installed on Centos 7, looked into the Apache settings looks good (we now have modules). Got Callum to change the name servers and get the domain up and running…
Everything went smoothly? and then Bang! 403 error not sure how the site could have a 403 because it has the interworx default page, and our index.php with a phpinfo echo in it.
I’m going to throw them an email later tonight to see what is in the works left to see if it’s a bug or something to get the pages working on the siteworxs, but for a RC I’m disappointed.
If you would like to try it out guys use the following command:
sh <((curl -sL interworx.com/inst.sh)) -r release-candidate
Will update the thread as I find out more. Fingers crossed we can get on Centos 7 before the new year.
I’m sure you know, but 403 is permissions error usually.
Do you have a htaccess file in hosting folder, I seem to remember this was an issue previously where it did not have the correct permission applied.
Just a thought but look forward to any updates
Many thanks
John[/QUOTE]
I do but didn’t when I tested it first, I was trying to use the .htaccess to bring up some errors in a error_log but nothing. all the folders /html/ etc is lcdev:lcdev and I believe they are 755 or whatever they are default’d too haha. can you try mate see if centos 7 works on your end too
Just a thought, but didn’t CentOS 7 bump Apache to 2.4, as to 2.2 from CentOS 6? Maybe there’s a config issue there in httpd.conf. I think it was related to that “Allow from all” directive.
Hi Liam
Good call, but it is already inlcuded.
I have finally loaded a centos7 and IW5.1 RC, and can see that the siteworx hosting account when added, is not restarting httpd, and interestingly, the webpage buttons do not work i.e if you click restart/stop/start on webserver page, they do not do anythhing, yet they show the action as completed.
I tested this by manually stopping httpd from ssh, then attempted to start the httpd from CP, so it does still need some work and vis versa.
Once though, when the siteworx account has been created, if you ssh into server, and manually restart httpd, the website becomes available. I tested this with 2.3sh.co.uk.
I might try to upgarde to Beta to see if anything has changed, as there appears to be issue with firewall not starting, and though I can manually start form ssh, it stops all web traffic.
Many thanks
John
Hi
I’m sorry, I just realised I was using wrong command for firewall from SSH (CP buttons do not work).
To start firewall, ssh into server and run service iptables start
to add for start on startup, run chkconfig --level 345 iptables on
Firewall now working
Many thanks
John
Jenna @InterWorx sorted the issue I had and it’s a bug:
Turns out there was a server issue hidden within a bug. There is a known bug in 5.1 where Apache does not restart automatically on Siteworx account creation. Manually restarting eliminates the 403 error.
PS: Ah John found it out earlier lol whoops. But yeah that’s the bug.
Hi
Liam, I myslelf do not believe it will be backported sorry, and only appears in centos7 iw-repo
I have reloaded centos 7 and interworx 5.1 release candidate, as upon server restart, things were not going well - IW would not start, mariadb not starting, firewall not starting…
Here is what I did to bring live and on restart of services/server
MariaDB
vi /etc/my.cnf
Uncomment out !includedir /etc/my.cnf.d so it reads includedir /etc/my.cnf.d
save
(this should bring up mysql and mariadb) check by service mysqld start
FIrewall
Centos 7 uses firewalld to control iptables, hence why iptables are not working, firewalld is not running, but if forewalld started, all access stops due to no rules.
I read that forewalld is mainly for workstations, but in the same reading, someone advised not using iptables but to use forewalld. For the moment, I will just use iptables and not firewalld (but you make your own choice), for iptables only
service iptables stop
systemctl mask firewalld
systemctl enable iptables
systemctl enable ip6tables
systemctl stop firewalld
systemctl start iptables
systemctl start ip6tables
vi /etc/sysconfig/iptables
add
-A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 2443 -j ACCEPT
save and start iptables - service iptables start
Iworx
Not yet found how to start after server restart but will come back to it
Restart server
SSH into server
Check the mysqld is running service mysqld status
check iptables running service iptables status
check httpd running service httpd running
check iworx running service iworx status (should show stopped)
start iworx service iworx start
This then should allow IW to work but I am sorry of this is wrong and please use only at your own risk
Many thanks
John
Hi
I tried logging back into IW and received the stack trace error, which has been noted previously, however Ramon posted how to correct this. I suppose a quick cheat would be to run cvspermfix.pex on a cron say every 24 Hours or so.
Also, I tried my posted method of restarting Iworx, which was not correctly working, but think this maybe because of some changes I had made, so I have posted in full the command to start IW, where it should start IW-DB and IW-web, check using service iworx status
I hope that helps a little
Many thanks
John
SSH into server
Stack trace failure Fix (credited to Ramon post)
cd ~iworx/bin
./cvspermsfix.pex
If having issues starting Iworx, please use this
/usr/local/interworx/etc/init.d/iworx start
I was not able to save the modified SSH settings and one time I had problem with permissions and a 403 error. Both can be repaired easy, now everything works fine! (Cents 7 XEN VPS, fresh install)
I installed it 10 days ago. It works perfectly after repairing the mentioned errors (Maybe I had to restart the firewall manually, but I did not remember exactly). Some of our users had to update their page because of the new php version updated to 5.6.x immediately.
The first installed version was 5.1.0-983. No updates arrived, this is the latest now. We are installed PostgreSQL too and also works fine outside IW.
And I discovered an other problem you can see here.
I think mostly IW works with centos 7, but it still has some issues, which manual intervention overcomes, but I would prefer myself to have it working as expected
As an example, when adding a new siteworx account to the CP, Apache does not restart (when it should) and hence the 403 error - a manual Apache restart resolved the 403 error
I understand though, centos 7 is a major change to how the code works, and there may well be code which is redundant but stopping normal function This though is my personal thoughts sorry and I could be wrong.
Dss, are you running in firewalld or iptables, if you don’t mind me asking. If firewalld, are you using BFD and is BFD correctly adding to iptables banned IP addresses.
Yeah, I realize that CentOS 7 is a major rewrite for an OS. But, there are a lot of great new features which is one of the main reasons I want to move to it ASAP. I just don’t want to have a production server to have service issues all the time.
Don’t know why, but I usually update SSH and other services manually instead of through the control panel. If all I have to do is restart httpd after adding a site, that’s no big deal. It sounds as if things are manageable. I may start playing with this weekend. I really appreciate all the input on this. It has helped me and I’m sure a lot of other people wanting to move to CentOS 7.
Last night I installed CentOS 7 on a server and I’m ready to install Interworx. Do you know what the latest version of Interworx is for the install script? Is the below (release candidate) the latest?
Yes, that’s the one I would use, release-candidate
Also, 5.1 has reached stable status, so unfortunately, our production servers were updated a few ago, when I didn’t want them updated yet. My bad though
Appreciate if you could update after with how you found it, but please have a quick read through my experience, which hopefully may help
not sure how the site could have a 403 because it has the interworx default page, and our index.php with a phpinfo echo in it.
There is a known bug in 5.1 where Apache does not restart automatically on Siteworx account creation. Manually restarting eliminates the 403 error.