#foswiki 2017-05-18,Thu

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***alexlist has quit IRC (Quit: Coyote finally caught me) [00:00]
..................................................... (idle for 4h21mn)
ChanServ sets mode: +o gac410 [04:21]
................................... (idle for 2h51mn)
ChanServ sets mode: +o MichaelDaum [07:12]
..................................................... (idle for 4h23mn)
ChanServ sets mode: +o Lynnwood [11:35]
.......... (idle for 47mn)
ChanServ sets mode: +o gac410 [12:22]
........................ (idle for 1h59mn)
ChanServ sets mode: +o Lynnwood__ [14:21]
.......................................................................... (idle for 6h5mn)
CHYCCan anyone explain why I don't get a textbox on edit pages after an upgrade to 2.1.3? Console looks OK. Seems to be broken in Chrome and Firefox
http://picpaste.com/screenshot-foswiki-jZTyhKe7.png
Downgrading to 2.1.2 works.
Any pointers gratefully received.
[20:26]
gac410Did you clear your browser cache? Maybe stale javascript? 2.1.2 to 2.1.3 wasn't a huge upgrade. Let me look at the release notes. [20:27]
CHYCDon't think it's browser cache as I installed Chrome just to try it! [20:28]
gac410In configure, did you visit the Extensions -> JQuery settings page and select the latest version of jquery?
If you run the Foswki page cache, did you refresh the cache as admin, visit any URL with ?refresh=all
If you are using fastcgi / mod_perl did you restart the web server?
None of these are specific to your situation. Just things I'm thinking of that might go wrong.
[20:29]
CHYCjquery was 2.2.3. Bumped it to 2.2.4 bumped, restarted apache, cleared cache in browser, visited ?refresh=all. Fraid it's still the same.
I'm thinking there's a wayward plugin somewhere
[20:34]
gac410Do you have any locally customized skin. Try running with the default SKIN=natedit,pattern [20:34]
CHYCNope, it's as vanilla as they come. [20:34]
gac4102.1.2 to 2.1.3 is a fairly minor increment. Not a lot of big changes. Are you getting any errors in the apache log or in the javascript console? Can you use browser tools to look at the requests for any 404's or other errors [20:35]
CHYCI get a window.controllers is deprecated warning in the browser, no 404s. [20:36]
gac410On foswiki.org we've pretty much continuously upgraded from 2.0 ... right up through the latest 2.1.4-RC2 that is on it now. I've not seen anything like this.
Look at System/PerlDependencies, and System/InstalledPlugins for any errors
er. Make that System/PerlDependencyReport
[20:37]
CHYCNo errors in apache logs.
I'm sure it's something very peculiar to my setup. I run some fairly exotic plugins.
Next step is to disable them one by one.
[20:39]
gac410If you have FOSWIKI_ASSERTS enabled in bin/LocalLib.cfg, you can use the "debugenabledplugins=...." query param to list the plugins you want active for a particular request. [20:41]
CHYCThat's very useful information. Thanks [20:42]
gac410How did you upgrade? Just unzip the 2.1.3 upgrade.tgz on top of your installation?
Doe the wikitext editor work? vs the TinyMCE editor. Or even the old plaintext editor (remove "natedit" from the skin setting.
[20:42]
CHYCI followed the instructions here: https://foswiki.org/Download/FoswikiRelease02x01x03#Upgrade_Instructions [20:44]
gac410See https://foswiki.org/Support/Faq68 ... which has examples of how to use that debug faciliity. However in 2.1.3 it's disabled unless foswiki debugging is active as it could be a way for security extensions to be bypassed.
So just an in-place upgrade using tar --strip-components=1 -zxf /path/to/Foswiki-upgrade-2.1.3.tgz
[20:44]
CHYCWell, I copied the directory first for an easier rollback. [20:46]
gac410;) yeah
Is this a public site?
[20:46]
CHYCFraid not.
How do I turn off natedit?
[20:46]
gac410remove the "natedit" from the SKIN=natedit,pattern
Hm I was able to recreate your issue by disabling javascript in my browser.
I'm guessing that something in javascript land is not loading or executing. but I really don't know what to look for.
Do you have SafeWiki plugin which does javascript signing, and block scripts if they are not correctly signed?
[20:47]
CHYCHooray, setting SKIN = pattern gets me to an edit page :) [20:51]
gac410okay. Do both the TinyMCE Wysiwyg editor and the plain text editor work? [20:52]
CHYCI'm afraid you're speaking to a noob. Here's a picture of what I have, and it seems to work http://picpaste.com/foswiki-working-BytOGZlm.png [20:54]
gac410Okay. That's the TinyMCE wysiwyg editor. So it is using javascript. [20:55]
CHYCI appreciate your help BTW. You've helped me loads already [20:55]
gac410but why natedit is toast ... I really have no idea. [20:56]
CHYCYes, it's bizarre what with no errors logged. [20:57]
gac410There are only 3 very minor changes to NatEdit between 2.1.2 and 2.1.3 Our primary Natedit developer is offline right now. [20:58]
CHYCThere's honestly no rush. TinyMCE may not look as shiny, but it seems to work so I'm much more relaxed than I was earlier :)
Many thanks gac410.
[20:59]
gac410yw. I wish I had more of a clue. It's either an issue in the templates, or something in the javascript. [21:00]
After the upgrade, make sure all files have correct ownership. chown -R your-web-user:your-web-group foswiki
the actual user/group depends on the web server & OS. Might be www, www-data, apache, or ???
[21:05]
CHYCYeah, I'm looking at that now.
Yes!! I did a recursive chown and it's all working
[21:06]
gac410Excellent!
There is a note about that on the upgrade page, but it's subtle. "Be sure to run tar as your web server user." I should add a comment that if things don't work, be sure to set the proper ownership.
I'll add a pointer to this. https://foswiki.org/System/InstallationGuide#Step_2:_Confirm_file_and_directory_ownership_and_permissions
[21:08]
................ (idle for 1h17mn)
daemonhey all, I am installing foswiki and was looking for a few pointers
I believe I have succesfully gone throuigh the config, got SSL in order and so
but when I visit my domain https://wiki.tmp.group
I get a 404, even though vhosts is loaded and I used the generator on the website
cannot seem to find any reason it would be 404'ing all the paths look correct
the vhost starts its define as https://paste.ee/p/qm0MU
[22:29]
............. (idle for 1h3mn)
gac410hi daemon ... What OS did you install on? [23:37]
daemongac410, freebsd
gac410, I realised though that fcgid was not installed, so I have added it now I am getting an error at least
[Thu May 18 23:37:54.530849 2017] [core:error] [pid 43809] [client 2001:470:1f09:101a:::62154] End of script output before headers: foswiki.fcgi
[23:37]
gac410If selinux or other mandatory access control is enabled that can make apache prevent execution. [23:38]
daemonselinux is not enabled [23:38]
gac410Check the server log files. There should be a log for the fcgi process I think.
er... no it should be the var/log/access_log and var/log/error_log
[23:39]
GithubBot[distro] vrurg pushed 1 new commit to Item13897: https://git.io/vHebk
distro/Item13897 7f153ad Vadim Belman: Item13897: Additional support for Unit::Leak::Object.
[23:41]
***GithubBot has left [23:41]
FoswikiBothttps://foswiki.org/Tasks/Item13897 [ Item13897: Implement ImproveOOModel proposal. ] [23:41]
daemongac410, https://paste.ee/p/kMiXp [23:41]
gac410that's not much :( I'm looking for some old notes I took a while back
I ran into an issue with the default shebang line in the scripts. We now default to "#!/usr/bin/env perl" which *should* pick up perl from the local environment and "just work" however it did not. I had to rewrite all the scripts to use /usr/local/bin/perl
[23:42]
daemonthere we go
just got rid of a rake of problems
I ran foswiki.fcgi direclty in perl
had some missing deps
just cleared them up
now lets see whats stopping it
[23:45]
vrurggac410: I've recently hit a problem with apache dropping off all but /bin and /usr/bin from the default PATH. This is where env stopped working – because perl is now /usr/local/bin on freebsd. [23:46]
gac410I don't know why /usr/bin/env perl doesn't work on freebsd. It works fine on linux [23:46]
daemonthe most useless error logging ever conceived
jesus really nothing more
[23:46]
vrurgFixed with manual SetEnv PATH in apache config. [23:46]
daemongac410, I use that env path on a few of my other scripts seems to work [23:46]
vrurgdaemon: Guess this is your case too.
They've silently changed something in apache port, I think.
[23:46]
daemonah
where is the paths I need to change (thisd is my first time using well .... apache (version 2) or foswiki :)
[23:47]
vrurgdaemon: the logging comes from the fact that env gives you no output and a bad exit code – that's all you eventually get in the log. [23:48]
gac410we have a script tools/rewriteshebang.pl it can rewrite all the shebang lines to wherever your [23:48]
vrurggac410: Nah, better don't do it.
daemon: Do you use virtualhost setup?
[23:48]
daemonvrurg, yes in combination with the generator on the website [23:48]
gac410daemon: vrurg does a lot more with freebsd. I'll defer to his advice. My solution - brute force - is to fix the shebangs ;) [23:48]
daemonhttps://paste.ee/p/XnodS#MqDvOKAUoF4k13qz6nxHhoP4oSEBuDP4
was the output for it
[23:49]
vrurgThen within virtualhost directive 'SetEnv PATH /bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin' must be sufficient. [23:49]
daemonvrurg, you would not by chance be the port maintainer would you [23:49]
vrurggac410: shebangs are good until you upgrade. Then you get the originals back – and voilà! [23:50]
gac410We don't have an official port. I have no idea who maintains it. Our only official distributions are the tar/zip files :( [23:50]
daemonvrurg, I have added it just below my servername in the virtualhost define [23:50]
vrurgdaemon: Nah, the only port I ever maintained was a backup app. Quit it as long as changed work. [23:50]
gac410vrurg, I'll add that to the ApacheConfigGenerator Thanks for the suggestion. [23:51]
daemonvrurg, I am still getting that the script exited prematurely [23:51]
vrurgHm... fcgid... That's worse. [23:51]
daemonworse than ... ? I can change to anything
this entire instance is just for this wiki :)
[23:51]
vrurggac410: Will for for CGI though. I'm ashamed, but my lazyness highnesty still using CGI for the corporate setup. ;) [23:52]
gac410daemon: tools/dependencies should check all the dependencies for you. fcgid is very good :P Much faster. [23:52]
vrurgdaemon: fcgi is good for speed, stick to it. The problem is that I don't rememeber where does it gets the PATH env from. [23:53]
daemonhttps://paste.ee/p/HOO1s
it seems quite happy looking at that script
[23:53]
gac410well to test daemon, you can edit the bin/foswiki.fcgi script and make sure the first line points to your executable perl. But as vurug says, You need to make sure you fix it if you upgrade. [23:53]
daemononce this is working I will be looking at that my self
because I acctually puiblish scripts that use /usr/bin/env perl
and they work perfectly well
[23:53]
vrurgAgree with gac. Test with full perl path in shebang and see if this is the case.
Narrow down possible variants range.
[23:54]
daemonthis is probably a remmeannt from the old old days [23:54]
gac410Email::Mime and Email::Simple are both required. I don't think foswiki will run without it. [23:54]
daemonbut should that be chmod +x ?
because as it stands it does not have the execute bit set
[23:54]
gac410yikes ... yes fcgi script should be +x [23:55]
vrurgvrurg silently murmurs in a corner: "PSGI doesn't have to be an executable..." ;) ;) [23:55]
daemonyes thats what sprung to mind as well ;)
the full path made zero difference nor did the execute bit
[23:55]
gac410well until foswiki 3.0 comes out hopefully this decade ... psgi doesn't matter. [23:56]
daemonhold on I think Igot more debug output
let me check
[Thu May 18 23:57:14.447299 2017] [fcgid:warn] [pid 49872] [client 2001:470:1f09:101a:::62285] mod_fcgid: stderr: ERROR: Could not open logfile /usr/local/www/foswiki/working/logs/error.log for write. Your admin should repair file or directory access permissions and/or ownership!
[Thu May 18 23:57:14.447326 2017] [fcgid:warn] [pid 49872] [client 2001:470:1f09:101a:::62285] mod_fcgid: stderr: ERROR: Could not open logfile /usr/local/www/foswiki/working/logs/error.log for write. Your admin should repair file or directory access permissions and/or ownership!
change a few perms..
[23:56]
gac410Ah... Installed as root? Need to be owned by the apache user [23:57]
vrurggac410: I'm just kidding. ;) [23:57]
daemonI installed the bloody freebsd package to hopefully not hit this [23:57]
gac410vrurg, don't say anything :D [23:57]
daemontime for an email to that maintainer
as it did not even include all the deps it needed either
and we have a site up!
[23:57]
gac410See Foswiki::System.SystemRequirements. We have an example "pkg install" command for freebsd [23:58]
daemonlots of warnings and errots [23:58]
FoswikiBothttps://trunk.foswiki.org/System/PerlDoc?module=Foswiki::System [23:58]
daemonbut at least its up [23:58]
vrurgdaemon: Congrats! [23:58]
daemonnow time to go set that end path back /usr/local/bin SHOULD work [23:58]
gac410damn bot gave wrong link [23:59]
vrurgBut I would suggest you avoid using foswiki port. Try manual install. Leave ports for dependencies. [23:59]
gac410Due to my typo Foswiki:System.SystemRequirements [23:59]
FoswikiBothttps://foswiki.org/System.SystemRequirements [ SystemRequirements ] [23:59]
gac410much better bot. thanks. [23:59]
vrurgFoswikiBot++ [23:59]
FoswikiBotvrurg: Karma for foswikibot is now 1 (thanks!) [23:59]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)