6.b6 still can't create Main Index [message #533] |
Tue, 30 May 2017 21:43 |
Mark Friedman
Messages: 18 Registered: August 2016
|
Junior Member |
|
|
Product: FoxTrot Pro 6.0 beta
I have sent several reports and logs on the other betas for v6. [Call To
Action] and have posted them in the forum.
I regret to report I cannot build a Main Index for 6.b6, either.
The Main Index (uncompleted) is 3.6GB. Has this exceeded some internal
limit?
From your console log:
------------------------------------------------------------ -----------
2017/02/14, 22:54:25 -0500: Starting Starter (pid=575)
2017/02/14, 22:54:25 -0500: Launched by launchd
starter server port = 49267
2017/02/14, 22:54:25 -0500: waiting connection on port 49267...
2017/02/15, 03:00:02 -0500: Launching indexer using high-level API ->
pid=3705 (index: /Users/mark/Library/FoxTrot/Main Index.ftindex)
2017/02/15, 03:00:04 -0500: Launching indexer using high-level API ->
pid=3708 (index: /Users/mark/Library/FoxTrot/synology.ftindex)
2017/02/15, 03:00:06 -0500: Launching indexer using high-level API ->
pid=3711 (index: /Users/mark/Library/FoxTrot/itunes local.ftindex)
2017/02/15, 21:18:32 -0500: ...client talking on port 49267...
2017/02/15, 21:18:32 -0500: ...client connected on port 49267
2017/02/15, 21:18:32 -0500: waiting connection on port 49267...
2017/02/15, 21:18:32 -0500: client thread 0x00007ffd95b38140 started
2017/02/15, 21:18:32 -0500: Launching indexer using high-level API ->
pid=23141 (index: /Users/mark/Library/FoxTrot/Main Index.ftindex)
2017/02/15, 21:18:35 -0500: Launching indexer using high-level API ->
pid=23145 (index: /Users/mark/Library/FoxTrot/synology.ftindex)
2017/02/15, 21:18:36 -0500: Launching indexer using high-level API ->
pid=23149 (index: /Users/mark/Library/FoxTrot/itunes local.ftindex)
2017/02/15, 21:36:12 -0500: Launching indexer using high-level API ->
pid=23538 (index: /Users/mark/Library/FoxTrot/itunes local.ftindex)
2017/02/15, 21:56:27 -0500: Launching indexer using high-level API ->
pid=24121 (index: /Volumes/FTIndex/synology.ftindex)
2017/02/15, 21:58:11 -0500: Launching indexer using high-level API ->
pid=24147 (index: /Volumes/FTIndex/Main Index.ftindex)
2017/02/15, 21:59:43 -0500: Launching indexer using high-level API ->
pid=24183 (index: /Volumes/FTIndex/itunes local.ftindex)
2017/02/16, 17:47:44 -0500: client thread 0x00007ffd95b38140 stopped
------------------------------------------------------------ -----------
2017/02/16, 20:07:56 -0500: Starting Starter (pid=551)
2017/02/16, 20:07:56 -0500: Launched by launchd
starter server port = 49264
2017/02/16, 20:07:56 -0500: waiting connection on port 49264...
I want to note that iTunes is on a sever on my network. The other network
volumes I've successfully indexed.
What additional information can I share with you to help you debug this
program?
|
|
|
Re: 6.b6 still can't create Main Index [message #534 is a reply to message #533] |
Wed, 31 May 2017 04:08 |
CTM Development
Messages: 57 Registered: April 2014
|
Member |
|
|
Sir,
Thank you for sending this report him. There is nothing obvious from looking at it initially, and I do not think you have hit any kind of hard limit. I'm asking my colleague to review this.
We will get back to you.
thanks,
jean michel/ ctm qa
> On 30 May 2017, at 15:43, Mark Friedman wrote:
>
> Product: FoxTrot Pro 6.0 beta
>
> I have sent several reports and logs on the other betas for v6. [Call To Action] and have posted them in the forum.
>
> I regret to report I cannot build a Main Index for 6.b6, either.
>
> The Main Index (uncompleted) is 3.6GB. Has this exceeded some internal limit?
>
> From your console log:
> ------------------------------------------------------------ -----------
> 2017/02/14, 22:54:25 -0500: Starting Starter (pid=575)
> 2017/02/14, 22:54:25 -0500: Launched by launchd
> starter server port = 49267
> 2017/02/14, 22:54:25 -0500: waiting connection on port 49267...
> 2017/02/15, 03:00:02 -0500: Launching indexer using high-level API -> pid=3705 (index: /Users/mark/Library/FoxTrot/Main Index.ftindex)
> 2017/02/15, 03:00:04 -0500: Launching indexer using high-level API -> pid=3708 (index: /Users/mark/Library/FoxTrot/synology.ftindex)
> 2017/02/15, 03:00:06 -0500: Launching indexer using high-level API -> pid=3711 (index: /Users/mark/Library/FoxTrot/itunes local.ftindex)
> 2017/02/15, 21:18:32 -0500: ...client talking on port 49267...
> 2017/02/15, 21:18:32 -0500: ...client connected on port 49267
> 2017/02/15, 21:18:32 -0500: waiting connection on port 49267...
> 2017/02/15, 21:18:32 -0500: client thread 0x00007ffd95b38140 started
> 2017/02/15, 21:18:32 -0500: Launching indexer using high-level API -> pid=23141 (index: /Users/mark/Library/FoxTrot/Main Index.ftindex)
> 2017/02/15, 21:18:35 -0500: Launching indexer using high-level API -> pid=23145 (index: /Users/mark/Library/FoxTrot/synology.ftindex)
> 2017/02/15, 21:18:36 -0500: Launching indexer using high-level API -> pid=23149 (index: /Users/mark/Library/FoxTrot/itunes local.ftindex)
> 2017/02/15, 21:36:12 -0500: Launching indexer using high-level API -> pid=23538 (index: /Users/mark/Library/FoxTrot/itunes local.ftindex)
> 2017/02/15, 21:56:27 -0500: Launching indexer using high-level API -> pid=24121 (index: /Volumes/FTIndex/synology.ftindex)
> 2017/02/15, 21:58:11 -0500: Launching indexer using high-level API -> pid=24147 (index: /Volumes/FTIndex/Main Index.ftindex)
> 2017/02/15, 21:59:43 -0500: Launching indexer using high-level API -> pid=24183 (index: /Volumes/FTIndex/itunes local.ftindex)
> 2017/02/16, 17:47:44 -0500: client thread 0x00007ffd95b38140 stopped
> ------------------------------------------------------------ -----------
> 2017/02/16, 20:07:56 -0500: Starting Starter (pid=551)
> 2017/02/16, 20:07:56 -0500: Launched by launchd
> starter server port = 49264
> 2017/02/16, 20:07:56 -0500: waiting connection on port 49264...
>
> I want to note that iTunes is on a sever on my network. The other network volumes I've successfully indexed.
>
> What additional information can I share with you to help you debug this program?
>
>
|
|
|