• After installing the cross-linker 1.4.0 update the serverload rise instantly up to an failure

    Message from syslogd@gxRPF at Tue Jan 13 22:21:22 2009 …
    gxRPF kernel: Trying to fix it up, but a reboot is needed
    Jan 13 22:21:22 gxRPF kernel: Bad page state at prep_new_page (in
    process ‘apache2’, page 0000010002957080)
    Jan 13 22:21:22 gxRPF kernel: flags:0x01100060
    mapping:000001007c784658 mapcount:1 count:1
    Jan 13 22:21:22 gxRPF kernel: Backtrace:
    Jan 13 22:21:22 gxRPF kernel:
    Jan 13 22:21:22 gxRPF kernel: Call
    Trace:<ffffffff801552f9>{bad_page+89}
    <ffffffff80155d70>{buffered_rmqueue+560}
    Jan 13 22:21:22 gxRPF kernel:
    <ffffffff80152709>{do_generic_mapping_read+1145}
    <ffffffff80155e5e>{__alloc_pages+174}
    Jan 13 22:21:22 gxRPF kernel:
    <ffffffff80161e54>{do_no_page+644}
    <ffffffff80162410>{handle_mm_fault+336}
    Jan 13 22:21:22 gxRPF kernel:
    <ffffffff8011f2f4>{do_page_fault+420}
    <ffffffff80164edd>{do_mmap_pgoff+1053}
    Jan 13 22:21:22 gxRPF kernel: <ffffffff80172a3d>{vfs_read+269}
    <ffffffff80110039>{error_exit+0}
    Jan 13 22:21:22 gxRPF kernel:
    Jan 13 22:21:22 gxRPF kernel: Trying to fix it up, but a reboot is needed

    after a reboot this happens again two times … I revert back to version 1.3.2, did a reboot again and everything is working smoothly again …

    could you see any relations?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Anonymous User 337827

    (@anonymized-337827)

    Hm… On my server and websites everything works fine. It must be somehow related to global variables as the process of loading data has been modified.

    In 1.4.0 data are loaded only once at the beginning. Previous versions of cross-linker data were loaded each time the function was called. The real difference is this:

    In 1.4.0 data are loaded into global variables, and thus when they’re loaded, there is no need to execute functions which load data from MySQL more than once. The result is: 1.4.0 is faster than previous versions.

    In versions lower than 1.4.0 cross-linker loaded data from MySQL each time the function was called. So… each post, each comment… If some post contained 50 comments, data were loaded 51 times during showing 1 single page (50 comments + 1 post). Imagine that you had 500 word:URL connections. That means 51×500 selected rows during loading 1 single page. This causes slow loading time.

    I’m going to modify the thing and make an option between using 1.4.0’s data loading algorithm or 1.3.2’s data loading algorithm… Until I find and fix the reason of this unexpected (and to me also weird) problem.

    Thread Starter derchris79

    (@derchris79)

    so if I have a post with 2 comments … I currently (1.3.2) have 330 queries … with 1.4.0 … I have over 750 querie …

    I have about 32 words linked to URLs

    Would it make sense if I install a cache module? could you recommende one?

    Anonymous User 337827

    (@anonymized-337827)

    In fact, in 1.4.0 there should be less MySQL queries, so it makes no sense to me :-S . Caching would be great, although I don’t know any caching plugin for WP yet.

    Anyway, wait and use 1.3.2 for now. I started working on ability to select the data loading algorithm + it will also offer loading data from text files. It will be OK.

    As soon as I finish and test the new version it will be released here.

    Anonymous User 337827

    (@anonymized-337827)

    Update:

    Please, update your crosslink.php and use this:

    https://www.aqua-fish.net/temp/crosslinker/shsc.php

    And let me know if it works, please.

    Thanks!

    Thread Starter derchris79

    (@derchris79)

    Thank you – I will try it later on and let you know.

    Thread Starter derchris79

    (@derchris79)

    It seems that this fixed the problem – is it version 1.4.1 or is it an other release? should I use 1.4.1 instead of the php you posted here?

    Anonymous User 337827

    (@anonymized-337827)

    1.4.1 is what I mentioned above, so you don’t need to upgrade. It’s the same except the version number in the crosslink.php and readme.txt.

    Thanks for telling me about the problem ?? .

    Thread Starter derchris79

    (@derchris79)

    No problem … is it now using the “new engine” or the old or was it an other bug/problem?

    Anonymous User 337827

    (@anonymized-337827)

    In fact it was my mistake. I forgot to declare $nn as a global variable and this caused the entire problem. Core is still the same. On many computers $nn was automatically 0, so it didn’t cause any overloading or crashing. But some servers assigned high or even infinite values to $nn… this led to overloading and crashes of some machines.

    Later I may upgrade it in order to be loading process purely text files-based (this will increase the speed), but for now everything is OK. Especially big blogs don’t suffer from often and unnecessary load of data from MySQL.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Plugin: Cross-linker] Problems after 1.4.0 Update’ is closed to new replies.