Wow… crazy..
Thank you for this heavy test… this helps a lot…
year working on this first scan… 80.000 and 170.000 files are quite a lot… 
… after the fist scan it should be not so heavly ressourcehungry.
Just that you know what it dose.. it “registers” all files and then process them thoruhgt all the different filters..
- identify them (if not done already)
- Create Tumbnails…
- check if its a mail data —> when so fulltext scanning
- check every file if it can be translated to text so it could be index…
normaly i lowerd the priority so low it should not cause to much trouble… i will check your logs…)
Ahoy @Paradoxon ,
I terribly sorry -
Well, I must create an another instance of Haiku Nightly or I may can use the Beta6 I created for the test purposes - as unfortunately I had to remove the service from my main Haiku Nightly -
It became unbootable .. again and again - no more beyond the appropriate icon - light up just like HERE
Something with the actual Haiku does not fit well. I know there can be unresolved Haiku issues too, but if the index_server installed - I’m sure, as when I deinstalled - even on this hrev59975 I can boot into Haiku as well as
- → with Legacy BIOS mode + bootman ( bootman in MBR – HaikuR1Nightly to boot )
or
- → using the haiku_esp’s Haiku UEFI bootloader on my USB thunbdrive (EFI bootloader in haiku_esp FAT, HaikuR1Nightly BFS, DATA_MEDIA, BFS, shared data FAT32 – partitons)
If I installed ‘index_server_debug’ on test R1BETA6 - I would inform you.
I do not preserve that (those)Haiku instance(s).
Apropos, instances, as I have a Haiku x86, so 32 bit R1Beta6 instance too - I had not checked your site:
- is your service is applicable for Haiku32 bit too ?.. if so, and you would need test on that too, write me.
Well, those instances are almost emprty not so much files there actually.to process them -
Thanks again for testing everything.. also it menat for you that it took your system down.. i am sorry for this inconvenience.
i am on the way to solve some of your problems.. for exampel i will index different volums now one after a nother.. to not reander your system unusable .. also dont sent updates so fequently…
At the moment i dont have a 32Bit installation… maybe later…
Just for the next time.. if it renders your system unbotable.. it would help a lot if you could two things…
- on bootup use spacebar or shift to use the bootscreen.. then select debugoutput.. then you / i can see where it hangs..
- after blacklisting it on the next boot up… secure the the last syslog.. and sent it ot me
/boot/system/var/log/previous_syslog
Well, something permanently went wrong in my nightly install. I can boot only with state of 5th of August that was hrev59933 - unfortunately I have next hrev59956, that locks Haiku in CD ROM mode.
I still had not downgraded permanently or opened ticket about latest versions as cannot bootable for me.
There was tickets about boot issues regarding R1B6 ands maybe for Nightly as well, as ACPI behaviour, I mean some tables inintialization and so was introduced and fixed, but seems my 14-15 years old Intel laptop does not tolerate well some new hardware requirements. Maybe I should renew the UEFI bootloader, however legacy also stops/hang at package opening icon, as the picture above shows.
I know the Haiku menu stuff - I wrote once .. but no problem -
I assumed as I solved my issues which I described .. I seemed enough experienced in your eyes ;j
Don’t feel sorry for me - I was volunteered by myself for the test - I was just had not payed enough attention that - this is my bleeding edge Haiku as well, I wanted to keep on goin’ further as containing many config uniquely I want to keep.
( I started to write this days before I completed the last sentence only now )
I think I switch from Mint and check upgrade to latest can fix my this install, or not. I saw many upgrades in the tube since days I left Haiku without visiting or check on from my safe Ark of “Mint”.
Hopefully this version fixes some of your problems…
Best ist to install the deug version 
This should have been fixed not long after that. You should be able to run pkgman full-sync from inside the hrev59933 state, which should upgrade you to a newer version that doesn’t have this problem.
1 Like
Ahoy !
Well, I had not updated stuff here -
I can boot into latest Haiku, if I shutdown not reboot .. as somehow somethings with improvements in ACPI or something else changed the shutdown and reboot stuff.
I also need into boot fully with Linux and shutdown - otherwise the Wifi led won’t boot and then the Haiku boot won’t be succeed.
Also I have to be more patient as the fourth icon with packagefs extraction status will last longer than before so I cannot decide if it stucks or not ? as normally took some 6-8 seconds, now it’s considerably more, so sometimes I walk away.
With 5th of August state with hrev59933 I can spare the long waiting.
Moreover last time I got BFS corruption with a force reboot, and I had not checked when I upgraded from hrev59988 to hrev60010, so now I started remove the wrong node stuff to have again a healthy BFS. Finally a bit bored to fight with in the weekend, so I stopped to fix it.
Soon I will continue the fix and I may open a ticket with syslogs.
I would like to have a lowgswitch on Nightly as a new level came, or downgrade and have the hrev number in the syslog file. I would like also to archive the logs. now we loose them. as overwritten – if not set a more number of logs than days of a week – as otherwise logs are overwritten with time.
Ah yeah, and I don’t have working wifi, but somehow the led should be show as working before Haiku boot - otherwise the boot will stuck at fourth icon. It is just observation - no understandable reason/evidence to relation from my side.
New testversion with at least two fixes