Tiki-KGB: 03lindonb r63169 10branches/17.x/lib/jquery_tiki/tiki-jquery.js * [FIX] Move ajax tikifeedback to top of page after 5 seconds rather than hiding
03lindonb r63170 10trunk/lib/jquery_tiki/tiki-jquery.js 10trunk * [MRG] Automatic merge, branches/17.x 63166 to 63169
03lindonb r63171 10branches/ 1016.x/lib/core/Feedback.php 1016.x/lib/smarty_tiki/function.feedback.php 1016.x/lib/jquery_tiki/tiki-jquery.js
[bp/r63014, r63166 and r63169][FIX] Ajax feedback wasn't appearing in some cases; when normal location is not visible, place ajax tikifeedback at top of viewport and move to top of page after 5 seconds; avoid using deprecated javascript escape function; move jQuery code to tiki-jquery; other optimizations
fabricius: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
olinuxx: joined #tikiwiki
joined #tikiwiki
fabricius: joined #tikiwiki
joined #tikiwiki
jonnyb: joined #tikiwiki
chibaguy: joined #tikiwiki
polom
jonnyb: pompom chibaguy
chibaguy: hello jonnyb
chibaguy_: joined #tikiwiki
jonnyb: Coo, two chibaguys! Hi both :)
chibaguy_: Heh, overload.
chibaguy__: joined #tikiwiki
Got this error after opening a page at dev.t.o to edit it: "Error
:
Read timed out after 10 seconds" -- Read timed out?
After editing and saving a wiki page at themes.t.o or dev.t.o, the edit url appears again and there's an error message in my browser: The dev.tiki.org page isn’t working
dev.tiki.org is currently unable to handle this request.
HTTP ERROR 500
Tiki-KGB: 03jyhem r63172 10trunk/lib/userslib.php * Fixed typo
chibaguy__: At dev.t.o/Bootstrap 3 to 4 transition (after editing) I get this error: Error
Unable to connect to es01.tiki.org:9200 . Error #0: stream_socket_client(): unable to connect to es01.tiki.org:9200 (Connection timed out)
Another question: should new users' names show up on "Since your last visit" at themes.t.o.? Asking because people can't actually register there.
jonnyb: sorry chibaguy__ - window got buried...
https://dev.tiki.org is taking ages to load...
chibaguy__: yeah, I noticed that too.
jonnyb: stacks of js errors :(
doc seems ok
polom Jyhem
nice timing :)
Jyhem: :)
jonnyb: dev seems to be rather non-responsive - just cleared caches and got a WSoD
Jyhem: no, I saw the messages
htop says memory is not eaten up
jonnyb: https://dev.tiki.org/Development seems to be taking 30 seconds to load...
Jyhem: the 4 procs go up and down but never reach 100%
jonnyb: it's arive but as chibaguy__ said with an error saying "Error: Read timed out after 10 seconds"
Jyhem: No nginx errors since 2017/07/01
jonnyb: https://tiki.org seems fine and quick
Jyhem: Ahaaa
www-data 30829 0.0 0.0 4340 656 ? Ss 05:00 0:00 /bin/sh -c cd /var/local/dev.tiki.org/www/; php console.php index:rebuild --log --cron
www-data 30831 0.4 2.1 549140 216812 ? S 05:00 2:52 php console.php index:rebuild --log --cron
right now
jonnyb: doc also fine so not a server-wide thing
Jyhem: yup, the only php console.php index:rebuild right now is about dev
jonnyb: mayhbe the elastic search server is struggling
yup, this time i got error: Unable to connect to es01.tiki.org:9200 etc...
Jyhem: Could php console.php index:rebuild be hitting elasticsearch too hard?
jonnyb: ping es01.tiki.org seems fine
maybe, there could be a regression in 17.x but it would have happened a few times before
sorry but i have to run away for a little while - maybe it will just go away when the rebuild has finished? :P
Jyhem: Let's hope so
-: Jyhem needs to eat now
Jyhem: unless anyone needs me to try something quick
jonnyb: does look like es01 is down, or at least struggling - amette, are you about?
amette_: joined #tikiwiki
polom
jonnyb: hi amette_
amette_: hi jonnyb - got your mail, looking in to it
jonnyb: thanks
amette_: Jyhem had a look into it and dev seemed to be in the middle of doing an index rebuild, in case that helps at all?
amette_: I now restarted the elasticsearch
so probably that index rebuild now failed
jonnyb: right
amette_: aaah, disk full
jonnyb: ah, again?
we just have too much stuff! :)
amette_: yep, yep
hrhr, yep
ok, gimme ten minutes, I have a plan
jonnyb: a cunning plan?
sorry, really need to pop out for a little while, bbl
robertokir: joined #tikiwiki
amette_: yep, it was quite cunning, es01 is back
and it's broken again...
... elasticsearch spits out gigabytes of logfiles, it's amazing.
RadoS: usefull?
-l
amette_: no, not really.
it the same stack trace over and over again a couple of times per second
got it fixed now though
rebuilt all indices
jonnyb: joined #tikiwiki
repolom
dev looks happy again, thanks amette and amette_ :)
amette_: wbolow
yeah, looks good. I really need to work on those machines a bit more. That disk resizing issue is most annoying.
Maybe next week. It should last a while now though.
jonnyb: nice, ta!
amette_: fun fact: 2/3 of the doc.tiki.org database is in the tiki_rss_feeds.ibd - a whopping 2.3GB - wtf!?
np, yw!
jonnyb: ah yes, i bet someone enabled some feeds and never looked after them - i added something to purge those tables, they're really just caches and shouldn't be in the db anyway...
on doc?
there are only 3 feeds, and two of them haven't updated since last september
amette_: Agreed. And even if they should be in the database... RSS feeds have only 20 items history or so by specification... 2.3GB need to be since the beginning of the internet.
jonnyb: i'll clear the caches but i guess the tables might need optimising? (overhead removing)
amette_: 406 in the database
many with last update "1", the others have proper time stamps
jonnyb: i just cleared the cache on the two seemingly dead ones
amette_: also very weird ones with names like "filegal.id=5e388103a391daabe3de1d76a6739ccd"
jonnyb: files? or tables?
amette_: ok, yes, optimizing did the trick. It's 9.3MB now.
9.0MB
jonnyb: super
amette_: and I meant RSS-feeds in the table tiki_rss_feeds - 406 of them
with those weird names
partly
jonnyb: in doc?
i only see 3...
amette_: weird
what are their names?
jonnyb: a sf.net one, news from doc and news from tiki.org
the sf one was borken so i'm fixing it
amette_: I do actually not understand how that table is supposed to be working...
and nope... not one of them has any name like those you mentioned
so there are no rss ids and we go by name... maybe... ok...
anyway.. not too critical now, I guess.
jonnyb: ah, those might be outgoing ones - i'm on external (incoming) ones
i think these live in tiki_rss_modules
and the cache is tiki_rss_items
amette_: aaah, ok. Then those names look a lot more reasonable
no, there's only a cache column in tiki_rss_feeds
jonnyb: weird, looking at the code it looks like it should be used but i don't get the difference between that one and tiki_rss_items
anyway, must get on - as you say, more next week maybe?
amette_: yep, sounds good. Thanks for your time!
left #tikiwiki
joined #tikiwiki
montefuscolo: joined #tikiwiki
amette_: left #tikiwiki
joined #tikiwiki
Telesight: joined #tikiwiki
robertokir: joined #tikiwiki
Tiki-KGB: 03chealer r63173 10trunk/lib/smarty_tiki/function.popup.php
[REF] Optimize
Remove some strange magic presumably not needed
03chealer r63174 10trunk/tiki-index.php
If no page is specified, report that even if we have permission to view
Presumably, this was meant to have the contrary behavior, but just reporting that no page is specified always seems better.
Fix message to reflect that a page_ref_id also works.
03chealer r63175 10trunk/lib/tikiaccesslib.php
[REF] is_machine_request(), is_serializable_request(), output_serialized(): Make static
03chealer r63176 10trunk/lib/tikilib.php * [REF] how_many_at_start(): Declare static
03chealer r63177 10trunk/lib/parser/parserlib.php * [REF] parse_data_process_maketoc(): Clarify (comments on headings)
03chealer r63178 10trunk/lib/core/Tracker/Field/Factory.php * [REF] getHandler(): Question check
amette_: left #tikiwiki
joined #tikiwiki
jonnyb: joined #tikiwiki
Tiki-KGB: 03chealer r63179 10trunk/lib/core/Tracker/Field/Text.php
[REF] processMultilingual(): Optimize
$data never has a "raw" member.
olinuxx: joined #tikiwiki
joined #tikiwiki
robertokir: joined #tikiwiki
amette_: left #tikiwiki
joined #tikiwiki
left #tikiwiki
joined #tikiwiki