Reindex totaly doesn't work in any way.
I can't see newly added tracks.

Code: [Select]

/usr/local/centovacast/bin/ccmanage reindex rtpdc --debug
Enter password for rtpdc: admin|xxxxxxx
Result: ERROR

/index.php?page=importmedia doesn't work as well

Result from Chrome developer tool (response from ajax triggered call
"http://domain.com:2199/client/rpc.php?m=progress.get_progress&r=59&r1=278134&s=rpcprogress&h=0&j=1"

Code: [Select]

callback: "progress_rpc_importmedia"
data: [import0.73428703, false]
type: "result"

text shown on "Import Media" page in "Log" box:

Code: [Select]

Updating media library, please wait...
Updated failed:

When using option to scan library in "Media" page I'm getting message "Complete" but nothing have been reindexed.

"Purge Library" Does not do anything as well.

There are a lot of thing that are starting to come up including re-indexing, 3.0 was doing good but 3.1 is causing a lot of headaches, should have just left it alone why o why do I keep updating

Headshaker: Sorry, I didn't make the association between this thread and your helpdesk ticket.  I've updated the ticket with a more useful response than I was originally able to provide.

My Auto DJ: We encountered a minor bug in v3.0.0 that required a fairly extensive change to fix, and unfortunately that caused a number of unanticipated regressions in v3.0.1.  I believe we've got most of them resolved now, but suffice to say I'm not pleased with how smoothly that went.

I should mention, though, that we are basically using major/minor/micro version numbers as "milestone tags" now -- sort of an indication to our clients that "enough things have changed now that it'd be a good idea to update".  But we are in fact doing continuous updates, and are pushing out new builds every few days (sometimes more often) as needed to fix bugs that have been reported.  So the turnaround time for bug fixes is extremely quick, even if they aren't announced immediately.  (And it never hurts to run sbin/update if you're having troubles with something -- it may have already been fixed!)

My Auto DJ: If you're still having reindexing issues, please feel free to post a new thread (or better, open a ticket) with the details.  Your issue is definitely not related to Headshaker's, as his was caused by a custom plugin he had created which was aborting the reindex job.

It is very rare, I think my problem had something to do with my cron issue anyway, all is well now