|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|
|Savi||Hey there everybody||[00:46]|
|Savi||may one here is my last chance to get foswiki finaly to work||[00:47]|
|gac410||What's going on||[00:47]|
|Savi||always getting 500 internal server error on a centos 7 on a digitalocean machine||[00:47]|
|gac410||What version of Foswiki?||[00:48]|
|Savi||dependency report is only showing optional not required packages
|Savi||let me have a look||[00:49]|
|gac410||Is digitalocean using cpanel ?||[00:49]|
|Savi||what do you mean with cpanel?||[00:51]|
|gac410||Some hosted sites require user to configure the service using a tool called cpanel.||[00:51]|
|Savi||seems this is 2.0.2, releaseHistory.html is showing only 2.0.2 as the last version||[00:51]|
|gac410||okay. There were changes in 2.0.3 to simplify cpanel setup. But sounds like that wouldnt' apply to you.||[00:52]|
|Savi||oh no, this is a hosting platform where you can get your own hosts, so I've root access to the server||[00:52]|
|gac410||Ah... okay. good.
Does anything at all work in the web interface?
Or is it always 500 internal erroor
|Savi||it's always 500||[00:54]|
|gac410||okay. Anything in the apache error log?
usually /var/log/apache2/error_log or similar
|Savi||End of script output before headers: view
AH01215: (13)Permission denied: exec of '/var/www/foswiki/bin/view' failed
|gac410||Ah.. okay that's better :)||[00:56]|
|Savi||End of script output before headers: view||[00:56]|
|gac410||What is output of 'ls -la /var/www/foswiki/bin/view||[00:57]|
|Savi||these are the last three lines in reverse order
-rw-r--r-- 1 apache apache 1938 Nov 21 18:38 /var/www/foswiki/bin/view
|gac410||Hm. they lost their execute attributes somehow. try chmod 755 /var/www/foswiki/bin/*||[00:58]|
|Savi||yeah, this is working against 500 but showing now another error||[00:59]|
|gac410||okay ... next ...?||[00:59]|
|Savi||Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information. ERROR: Could not open logfile path for write. Your admin should 'configure' now and fix the errors!||[00:59]|
|gac410||Okay. It sounds like all your permissions have gotten messed up somehow. Did you extract the tarfile locally?||[01:00]|
|Savi||yes I did, this is probably a result of why I got this now||[01:00]|
|gac410||I'm looking around .. Somewhere we have some recommended commands to reset all of the permissions.||[01:01]|
|Savi||it worked someday and now after I wanted to load all the data from a git repo back, nothing worked anymore
oh no, what a mistake don't think of the permissions
|gac410||Basically Everything needs to be owned by the web server user. Usually www-data or www or apache ... varies by system. :(||[01:02]|
I did chown -R apache:apache /var/www/foswiki after pulling from git repo
but that seems to be not enough
|gac410||It's not as simple as a chmod across the whole install. different files have different permissions.
I'm still looking. We have something somewhere on the support web.
|FoswikiBot||http://foswiki.org/Support/SettingFileAccessRightsLinuxUnix [ SettingFileAccessRightsLinuxUnix ]||[01:05]|
|Savi||that's very kind||[01:05]|
|gac410||It's a bit old, but should be fine for Foswiki 2.0 I have not had to review it in a long time.||[01:05]|
|Savi||ok, let's try it, than you've a review||[01:06]|
|Savi||wohoo, seems to work
|gac410||great. If the script at the top of that topic didn't do it, there is another more recent one at the very bottom.||[01:08]|
|Savi||I tried the one at the very top
and there are of course a few errors
will try the shell script at the very bottom now
|gac410||okay good. What I ought to do in my copious free time is to pull this into an appendix of the InstallationGuide, or even distribute it as a utility script.
btw, caution.... The script sets global permissions. If the server is shared, you might want to crank them down a bit.
Configure will probably complain about world readable/writable files.
anyway, you saved my day!
|gac410||Glad to help.||[01:14]|
|Savi||thank you a lot, and if you someday in Hamburg germany, I owe you a beer!||[01:14]|
|gac410||Sounds good :)
There are a few fixes in 2.0.3 that you might want to grab ... performance related to perl & unicode, and some minor security stuff.
*should* be safe to just extract the Foswiki-upgrade-2.0.3.tgz over the top of the install.
cd /var/www/foswiki; tar --strip-components=1 -zxf Foswiki-upgrade-2.0.3.tgz
|Savi||will sort that when I'm ready with understanding what is happend and automated the installation of the server completely||[01:17]|
|gac410||git should preserve permissions. They seem pretty stable here and we do all our development switching between various branches in git.||[01:17]|
|Savi||means that also should fix the permission issue?||[01:17]|
|gac410||hm, yes it should.
well it excludes files that are normally tailored, so not 100%
WebHome topics, WebPreference. etc.
|Savi||is there another mirror for foswiki-upgrade-2.0.3.tgz?||[01:24]|
|gac410||hm Sourceforge ... they have multiple mirrors. We don't host the files ourselves.||[01:25]|
|Savi||ok, this is only a question because I don't like them anymore ... not a debate on principles
upgrade works ... thanks again
|gac410||Occasionally for early beta's we'll load files onto Foswiki.org. But most come from sf. Github isn't all that great for hosting big zipfiles. And the github "release" process doesn't do stuff like minify js & css, etc.||[01:30]|
|Savi||this wasn't a plea for github at all, I only like the behaviour of sf regarding malware injections and those bad press||[01:34]|
|gac410||yeah. That's what I figured. we looked around a bit when the publicity started up. but didn't find anything that jumped out as ideal
We won't have any injection problems ... not with what we distribute anyway, and it's all checksummed and gpg signed
All our sourcecode is now on github. https://github.com/foswiki/distro
Also this summer right when we were trying to get 2.0 released they had a week+ outage. That hurt.
sf that is, not github
|Savi||I see, that's really bad, there are some initiatives that want to solve those problems in the future
but other question, did you ever heard from somebody that automated his deployment with ansible?
|gac410||No, not ansible. I know we have a dev working on a Vagrant automation.||[01:38]|
|Savi||a pity, but anyway
I try to get an automation working for a few foswiki installations distributed on 5 to 10 servers connected over wan and load balanced using dns
|gac410||wow ... cool. There are so many deployments we don't know about.
btw if you are using 2.0 and have significant performance needs, it may be worth looking at perl 5.20 Older perl has a regex performance bug with UNICODE. regexes fall back to the slow path.
|Savi||if my boss is giving me enough time I will anyway write a success story which I also can share with you guys if you want||[01:42]|
|gac410||cool. That would be great.
2.0.3 performance fixes were related to avoiding some regexes that were really heavy hitters.
|Savi||after reinstalling the server now with a fresh upgraded and pushed git repo I get the following error which leads me again to a permission problem?
ERROR: Could not open logfile /var/www/foswiki/working/logs/error.log for write. Your admin should 'configure' now and fix the errors!
|gac410||yeah. working/logs/* need to be writable
but configure cannot fix that type of error. hm bogus log message as well :(
|Savi||the funny thing is, it is writable||[01:55]|
|gac410||hm How about directory
If the open of the logfile fails. we test !-w, If that returns as not writable, we generate that "helpful" message. Otherwise we die with the actual failure.
If it's writable, could be ownership changed? root vs apache?
|Savi||yeah, it was the ownership
puh, ok, it's 3am and I need to go to sleep I guess
|gac410||okay... goodnight. :) hit us back up if you have more issues.||[02:03]|
|Savi||will dream about it, but thanks, thanks again||[02:03]|
|gac410||yw. Glad to help||[02:04]|
|................ (idle for 1h17mn)|
|GithubBot||[distro] gac410 pushed 4 new commits to master: http://git.io/vBe4e
distro/master 3b83500 George Clark: Item13504: Update error message...
distro/master a43afd5 George Clark: Item13504: MANIFEST permissions are inconsistent
distro/master b5ef863 George Clark: Item13865: Don't detect ,pfv directories as webs.
|***||GithubBot has left||[03:21]|
|FoswikiBot||http://foswiki.org/Tasks/Item13504 [ Item13504: Documentation changes Foswiki 2.0.x / 2.1.0 ]
http://foswiki.org/Tasks/Item13865 [ Item13865: Configure file permissions checker detects ,pfv directories as possible webs. ]
|...... (idle for 25mn)|
|***||WikiRingBot has quit IRC (*.net *.split)
fsfs has quit IRC (*.net *.split)
donbarry has quit IRC (*.net *.split)
jast has quit IRC (*.net *.split)
ChanServ has quit IRC (*.net *.split)
jayen_ has quit IRC (*.net *.split)
FoswikiBot has quit IRC (*.net *.split)
alexlist has quit IRC (*.net *.split)
|asimov.freenode.net sets mode: +ovo Lynnwood_ FoswikiBot ChanServ||[03:56]|
|ChanServ sets mode: +o SvenDowideit||[04:02]|
|............... (idle for 1h10mn)|
|ChanServ sets mode: +o Lynnwood||[05:12]|
|........................... (idle for 2h11mn)|
|ChanServ sets mode: +o CDot||[07:23]|
|..................................... (idle for 3h2mn)|
|ChanServ sets mode: +o Lynnwood||[10:25]|
|.............................................. (idle for 3h47mn)|
|ChanServ sets mode: +o gac410||[14:12]|
|................................ (idle for 2h39mn)|
|geetar has left||[16:51]|
|.... (idle for 17mn)|
|geetar has left||[17:08]|
|................... (idle for 1h30mn)|
|ChanServ sets mode: +o Lynnwood||[18:38]|
|.................... (idle for 1h35mn)|
|JulianLevens||gac410: I could conceivably have backlinks added to query search by 1st Dec; refactoring (*all*) the impacted elements in templates and other perl modules is likely to take quite a bit more time||[20:13]|
|gac410||I'd suggest getting started in a feature branch ... See how it goes.||[20:14]|
|JulianLevens||Of course I'll know better by the release meeting on 30th Nov
y, I'll create a feature branch
|gac410||It can factor into decisions on delay or not.
I'm on a branch completely reworking DefaultUserRegistration. I **hate** that page with a passion. It's so darn complex.
|JulianLevens||Sure, anyway I'm off to bed early for a change :)||[20:16]|
|gac410||Started to implement a "simple feature" ha... add templatetopic urlparam to registratoin.
okay... have a good night. Thanks JulianLevens
|***||JulianLevens has left||[20:16]|
|......... (idle for 41mn)|
|ChanServ sets mode: +o Lynnwood||[20:57]|
|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|