Question

Indexing services pauses ? Way to restart it via command prompt ?

Version 9 Administration

Updated February 12, 2016

asked on January 19, 2016

I noticed the laserfiche indexing gets paused and I have to manually go into the LF admin console and start it up, the LF full search indexing services is running fine and started (though in admin console it says indexing is paused ?) but the indexing gets paused. Is there a way to start or check on indexing services so its always running ?

Any ideas or suggestions how to make sure the indexing service is always in running state ?

0 0

Replies

replied on February 4, 2016

Hi Sumeet,

The issue mentioned by Anita will only occurs after LF Server is rebooted. It happens on LF 9.2 and later version. If that is your case, the scheduled indexing does not resolve the problem because LF Server will not respect the schedule. The following script may help to resume index queue automatically.

ResumeIndexQueue.vbs:

set args = wscript.Arguments
if args.Count = 5 then
    lfso = wscript.Arguments(0)  'e.g. LFSO100
    serverName = wscript.Arguments(1)
    dbName = wscript.Arguments(2)
    username = wscript.Arguments(3)
    password = wscript.Arguments(4)
end if

set app = CreateObject(lfso & ".Application")
set serv = app.GetServerByName(serverName)
set db = serv.GetDatabaseByName(dbName)
set conn = CreateObject(lfso & ".Connection")
conn.UserName = username
conn.Password = password

conn.create db

On Error Resume Next
if db.IndexStatus.Status = 4 then
	db.IndexStatus.Resume
end if

For example, you can use

ResumeIndexQueue.vbs LFSO100 localhost repositoryname admin password

If LF Server didn't reboot when you encounter the problem, please check the connection between LF Server and LF Full-Text Search Engine. If the problem persists, please contact your VAR about opening a support case for this.

For your latest reply, the folder you place QuitePeriods.xml is right. The time period seems wrong, where the end time should not be earlier than the start time. If you want to resume indexing every 7:00AM you can set it like <Period>1,6:55-1,7:00</Period> so that indexing will not effect much, or <Period>1,19:00-2,7:00</Period> which will pause indexing in the evening and resume it in next morning.

1 0

replied on February 2, 2016

Hi Sumeet,

The index state should be restarted from the admin console rather than command prompt. However, if your indexing keeps pausing unexpectedly (while the Laserfiche Full Text Search Service is still running) it's probably caused by certain errors within the indexing process, like if the Laserfiche server can't connect to the Full Text Search fro 15 minutes or so. If this is the case, you'll need to start the indexing through the admin console yourself. The LF 10 Service Pack 1 will fix this issue (due for release this year) by enabling the index queue to auto recover. For now, you could probably write a script to resume indexing automatically.

It's also possible to have indexing scheduled for certain times of the day, which could avoid server connection issues during high-traffic hours. This will automatically pause indexing and restart it based on the times you input. If your system's indexing pauses at the same point every day, it's worth looking into whether this is a setting that's enabled on your system.

0 0

replied on February 3, 2016 • Show version history

Lets hope this code i placed in quiteperiods.xml in the search folder will help me, good to know that after 15 mins of not being able to reach search/indexing server it will get paused, did not know that. I hope i do not have to do anything special i placed the above file where "catalogconfig.xml" sits in the Search folder on server. I hope i placed it in the right location, please let me know the exact path if that's not the right one.

<?xml version="1.0" encoding="utf-8"?>
<LFFTS>
<Catalog>
<Period>1,19:00-1,7:00</Period>
<Period>2,19:00-2,7:00</Period>
<Period>3,19:00-3,7:00</Period>
<Period>4,19:00-4,7:00</Period>
<Period>5,19:00-5,7:00</Period>
</Catalog>
</LFFTS>

0 0

replied on February 4, 2016 • Show version history

I will give the vb script a try, just did not want to store sql password or any passwords in the open sort of speaking, but the code i created(which ofcourse did not work, i hope its not in the wrong location, we are on 9.2 ver) I found on the LF kb as linked by Anita, the KB says this is the proper format, where stop time is before start time.

Paste the following into the XML file.

<?xml version="1.0" encoding="utf-8"?>

<LFFTS>

<Period>DayCodeStop,TimeStop-DayCodeStart,TimeStart</Period>

</Catalog>

</LFFTS>

Example: The following code would stop indexing at 7am on Monday and begin it again at 7:30pm on Monday:

right from here : https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-us/administration/Default.htm#../Subsystems/LFAdmin/Content/scheduled_Indexing.htm

0 0

View 2 previous replies

replied on February 4, 2016

Hi Sumeet,

I believe Ziyan was referring to the snippet of code you posted previously. For example, "<Period>1,19:00-1,7:00</Period>" means that indexing will pause at 7:00 PM on Monday and resume at 7:00 AM on Monday, which doesn't really work.

To denote a pause overnight, you can change the number before the time to indicate the day of the week. If you wanted to pause the indexing at 7:00 PM on Monday and resume on Tuesday at 7:00 AM, here's what you would use:
<Period>1,19:00-2,7:00</Period>.

0 0

replied on February 5, 2016

Yes, what Anita said about the format of period is right.

Since the issue to be fixed just happens after LF Server is rebooted, it should rarely happens. You may simply resume indexing manually before related hotfix comes out.

The script also supports using Windows Authentication by leaving username and password empty. For example,

ResumeIndexQueue.vbs LFSO100 localhost repositoryname "" ""

0 0

replied on February 5, 2016

oh i see it now what they have done and the formatting required, so this is a known issue/bug with indexing services ? "related hotfix comes out." hmm there is something in works I am assuming, i will try modifying my code and see if that makes any difference. If not will try the script next.

0 0

replied on February 5, 2016

Yes, this is a known issue (Actually with Laserfiche server instead of indexing service. And that's why quiteperiods.xml doesn't help.)

0 0

replied on February 12, 2016

Bumer.. i hope a fix will be coming out for this because daily task now is to restart the indexing service manually for time being.

0 0

You are not allowed to follow up in this post.

Question

Question

Indexing services pauses ? Way to restart it via command prompt ?

Replies

Sign in to reply to this post.