#267608 - 19/10/2005 23:49
3.00 alpha 13, rebuilding music database every time!
|
journeyman
Registered: 08/08/2002
Posts: 57
|
I recently upgraded my MkIIa from 2.0beta13 to 3.0alpha11. I partitioned a new hard drive manually and applied the software (3.0alpha13), then transfered all my fids from my two previous drives using cp -auvfx and am running it as a single drive unit for the time being. I am running Hijack 440 and telnetd. I have also modified player using set_empeg_max_fid.v7. I have not added any memory to my unit and I do not have a ReserveCache statement in my config.ini.
The problem came about when I began adding more music to the player. I had a few hundred albums to add, and I found trying to add them all at once choked jEmplode v70 (was running out of java heap space, I think). I would be interested to know if there is a solution or workaround to this problem. Running under Linux.
So I began adding my albums in 50 album chunks to get around this memory issue. After doing so twice (adding 100 albums), the next time I resrtarted the player, it rebuilt the music database. Now it does it every time, sometimes giving me a segfault before it gets to 100% complete. I am unable to run jEmplode, Emplode 2.00 or 2.10.
I have been through this forum and the FAQ looking for answers, but nothing seems to solve my problem. I have manually rebuilt the database, I have tried player -i, and I have fsck'ed many times.
Here is the error I get when trying to manually rebuild the database:
player.cpp : 587:empeg-car 3.00-alpha11 2005/07/25.
! tags.cpp : 61:Failed to open tags (0xc0041002).
! memory_stream.cpp : 42:MemoryStream failed to allocate memory.
! memory_stream.cpp : 42:MemoryStream failed to allocate memory.
! tunedb_disk.cpp : 878:Failed to build database. Bad. 0xc007000e.
! fidfile_disk.cpp : 1214:Why did write return zero for offset=0, size=0?
! fidfile_disk.cpp : 1214:Why did write return zero for offset=0, size=0?
Prolux 4 empeg car - 2.1485 Jul 25 2005
Vcb: 0x4073a000
Any help would be greatly appreciated.
|
|
Top
|
|
|
|
|
#267609 - 20/10/2005 08:06
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
carpal tunnel
Registered: 15/08/2000
Posts: 4859
Loc: New Jersey, USA
|
That memory allocation failure is the key. The alphas require more memory than the 2.0x versions of the player, and if you are memory constrained (Mark2 12MB or even sometimes Mark2a with 16MB), the player application does not have enough room to generate the database image in memory.
Try redoing the manual database rebuild, but make sure you turn on swap first:
swapon /swapfile
_________________________
Paul Grzelak
200GB with 48MB RAM, Illuminated Buttons and Digital Outputs
|
|
Top
|
|
|
|
|
#267610 - 20/10/2005 14:42
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: pgrzelak]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
Thanks for the reply Paul.
As mentioned I have a Mk2a (16 MB). I also mentioned I have tried manual rebuilds, each time with "swapon /swapfile".
I am currently at about 12,000 tracks.
Do I need a ReserveCache entry in config.ini?
|
|
Top
|
|
|
|
|
#267611 - 20/10/2005 15:11
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
carpal tunnel
Registered: 15/08/2000
Posts: 4859
Loc: New Jersey, USA
|
Okay. I had not noticed the swapons...
The only thing I can say is that random searching showed it to be a potential alpha bug. Can you try downgrading to 2.0, make sure your database can build there, and then reupgrade to the alpha?
_________________________
Paul Grzelak
200GB with 48MB RAM, Illuminated Buttons and Digital Outputs
|
|
Top
|
|
|
|
|
#267612 - 20/10/2005 15:46
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: pgrzelak]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
I guess I never mentioned the swapons.
Sure, I'll try downgrading to 2.0 final. Can you tell me exactly what happens during an upgrade (downgrade). Which files/directories are affected. If I have third party utilities installed, will they get overwritten/deleted? Which directories are safe to store such stuff?
|
|
Top
|
|
|
|
|
#267613 - 20/10/2005 15:56
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
carpal tunnel
Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
|
Upgrades completely overwrite all the root filesystem and the kernel in flash. You'll have to reinstall everything. Best case scenario is that you installed the binaries somewhere other than the root partition and you just have to reenable them (and, with the telnetd, recreate the devices), but it's still not totally trivial.
_________________________
Bitt Faulk
|
|
Top
|
|
|
|
|
#267614 - 20/10/2005 15:57
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: pgrzelak]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
Quote:
Can you try downgrading to 2.0, make sure your database can build there, and then reupgrade to the alpha?
To clarify: Paul is suggesting this to test if the problem is a 3.0 bug. Since 2 and 3 use different databases, you can't get a working database3 out of a database2 build. So even if 2.0 works, that doesn't mean your problem is solved.
Well, then again... Why are you running 3.0 at all? It's an alpha, it's got bugs. Is there some feature in 3.0 you can't live without?
|
|
Top
|
|
|
|
|
#267615 - 20/10/2005 16:05
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: wfaulk]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
Bitt,
To clarify, does the root filesystem include everything except /drive0 and /drive1? To have my utilities and config stuff (like config.ini) survive an upgrade, could I just store them in a directory in /drive0?
|
|
Top
|
|
|
|
|
#267616 - 20/10/2005 16:11
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: tfabris]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
Quote:
To clarify: Paul is suggesting this to test if the problem is a 3.0 bug. Since 2 and 3 use different databases, you can't get a working database3 out of a database2 build. So even if 2.0 works, that doesn't mean your problem is solved.
Yup, I understood that.
|
|
Top
|
|
|
|
|
#267617 - 20/10/2005 16:16
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
carpal tunnel
Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
|
I don't have an empeg I can log into in front of me, but I want to say yes. There is the music data partition, the root partition, the swap partition, the dynamic data partition (for bookmarks, current running lists, EQ, etc., and it's not a mountable filesystem), and a blank partition. And that's on each drive.
Wait. There's bound to be a FAQ for this. Hmm. Not really.
Anyway, it overwrites the root partition and that's it as far as the hard disk. (It actually overwrites it with a filesystem image, so there's no way to keep data there during an upgrade.) You can keep files in /drive0 and you can actually create a new filesystem on that blank partition. Neither of those will get deleted during an upgrade.
_________________________
Bitt Faulk
|
|
Top
|
|
|
|
|
#267618 - 20/10/2005 16:58
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
Quote:
To have my utilities and config stuff (like config.ini) survive an upgrade, could I just store them in a directory in /drive0?
Config.ini is already on /drive0, (/drive0/var if I recall correctly) so you don't need to worry about that.
I don't know where your utilities are stored, but I *always* put mine somewhere on /drive0 by default, for that very reason.
Please note that if you have any utilities that run automatically at empeg startup, if they are on /drive0 when they run, they will lock the /drive0 filesystem open and cause synchs and such to fail unless you run them in @DC mode only.
|
|
Top
|
|
|
|
|
#267619 - 20/10/2005 17:03
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: wfaulk]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
Quote:
You can keep files in /drive0 and you can actually create a new filesystem on that blank partition. Neither of those will get deleted during an upgrade.
Where is that blank partition located? I guess it isn't mounted by default? How could I mount it automatically at boot time?
|
|
Top
|
|
|
|
|
#267620 - 20/10/2005 17:16
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: tfabris]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
Quote:
Quote:
To have my utilities and config stuff (like config.ini) survive an upgrade, could I just store them in a directory in /drive0?
Config.ini is already on /drive0, (/drive0/var if I recall correctly) so you don't need to worry about that.
I don't know where your utilities are stored, but I *always* put mine somewhere on /drive0 by default, for that very reason.
Please note that if you have any utilities that run automatically at empeg startup, if they are on /drive0 when they run, they will lock the /drive0 filesystem open and cause synchs and such to fail unless you run them in @DC mode only.
I have most set to run in @DC mode, so they could reside on /drive0. The only one I run in @AC mode is telnetd, therefore that one can't reside on /drive0. I am curious about the blank partition that Bitt was talking about. That might be a nice solution.
|
|
Top
|
|
|
|
|
#267621 - 20/10/2005 17:18
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
Quote:
The only one I run in @AC mode is telnetd, therefore that one can't reside on /drive0
Um, did you try temporarily removing that from config.ini and doing your database build over again?
Since it's a running-out-of-memory issue with the player software, perhaps removing things that use up memory will help.
|
|
Top
|
|
|
|
|
#267623 - 20/10/2005 18:48
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
enthusiast
Registered: 11/06/2003
Posts: 384
|
Quote:
Where is that blank partition located? I guess it isn't mounted by default? How could I mount it automatically at boot time?
Doing this gets pretty unix-geekish. So unless you're real comfortable with that kind of stuff, you're going to be heavily dependant on the kindness of people to explain things, and they're not likely to remember all of the tiny details necessary to step by step someone through it who doesn't know what they're doing.
So with the disclaimer out of the way:
developer version of the software
console shell access (maybe you can do this with hijack's ftp site commands, much more tedious)
unused slice is hd[a|c]2
format slice, see roger's page about manual mkfs'ing
find "preinit" and save it as /bin/hijack (mlord's hijack kernel will run this automatically)
create a dir to mount this at, many use /programs0
edit fstab or mnttab as you like
mess with the preinit scripts and/or hijack menu options to do stuff.
Roger or Peter put together a tarball of some supplemental libraries and utils which are v. nice including a multi-location configuration switcher
There's a telnetd out there as well
I've got a whole bunch of these bits rolled up as a tarball that I can unroll after changing versions to put all of these in place, and honestly I don't remeber exactly all of the small bits.
--Nathan
|
|
Top
|
|
|
|
|
#267624 - 20/10/2005 18:53
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
enthusiast
Registered: 11/06/2003
Posts: 384
|
Overall, don't run v3[bold]alpha[/bold] unless you have to.
The occasional problems are worth it to me for ogg vorbis support, but if all I had were mp3 files I wouldn't bother.
--Nathan
|
|
Top
|
|
|
|
|
#267625 - 20/10/2005 19:52
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: Mataglap]
|
carpal tunnel
Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
|
Quote:
"preinit"
I think Hijack itself can do everything that my preinit did, so I'd probably suggest going that route. Nice to know people liked it, though.
_________________________
Bitt Faulk
|
|
Top
|
|
|
|
|
#267626 - 20/10/2005 20:37
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: wfaulk]
|
carpal tunnel
Registered: 24/12/2001
Posts: 5528
|
Quote:
Quote:
"preinit"
I think Hijack itself can do everything that my preinit did, so I'd probably suggest going that route. Nice to know people liked it, though.
I'm still using preinit actually. Never got around to removing it and it has been working fine ever since I installed it.
|
|
Top
|
|
|
|
|
#267627 - 20/10/2005 21:03
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: wfaulk]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
Quote:
Quote:
"preinit"
I think Hijack itself can do everything that my preinit did, so I'd probably suggest going that route. Nice to know people liked it, though.
I agree. It looks quite straight forward to get Hijack to mount hda2 using ;@EXEC_ONCE, and then use ;@MENUEXEC to launch userland programs.
|
|
Top
|
|
|
|
|
#267628 - 21/10/2005 05:37
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: pgrzelak]
|
journeyman
Registered: 08/08/2002
Posts: 57
|
Quote:
The only thing I can say is that random searching showed it to be a potential alpha bug. Can you try downgrading to 2.0, make sure your database can build there, and then reupgrade to the alpha?
Ok, I downgraded to 2.00 final, and the manual rebuild worked no problem.
But, I still seem to be having problems.
After the downgrade, I reinstalled Hijack 440, and tried uploading 1.4 GB of tracks using jEmplode v70 under Linux using ethernet. Firstly, jEmplode took a very long time loading the databases and then becoming responsive -- about 5 minutes! I had about 13,000 tracks loaded at the time.
After the tracks were uploaded, I got the following error from jEmplode:
Unable to synchronize with the current device. caused by:
Failed to synchronize with device. caused by:
Unable to open connection to device. caused by:
org.jempeg.protocol.ConnectionException: Failed to connect to the specified device. Please verify the device's IP address.
at org.jempeg.protocol.SocketConnection.open(SocketConnection.java:149)
at org.jempeg.empeg.protocol.EmpegProtocolClient.open(EmpegProtocolClient.java:359)
at org.jempeg.empeg.protocol.EmpegProtocolClient.open0(EmpegProtocolClient.java:1068)
at org.jempeg.empeg.protocol.EmpegProtocolClient.getStorageInfo(EmpegProtocolClient.java:881)
at org.jempeg.protocol.AbstractSynchronizeClient.computeFreeSpace(AbstractSynchronizeClient.java:343)
at org.jempeg.protocol.AbstractSynchronizeClient.synchronize(AbstractSynchronizeClient.java:308)
at org.jempeg.manager.SynchronizeUI.synchronize(SynchronizeUI.java:109)
at org.jempeg.manager.SynchronizeUI$1.run(SynchronizeUI.java:65)
at java.lang.Thread.run(Unknown Source)
It seems like all the files made it across OK, but the databases didn't get written, and I was forced to build them manually again.
Any ideas?
|
|
Top
|
|
|
|
|
#267629 - 21/10/2005 13:10
Re: 3.00 alpha 13, rebuilding music database every time!
[Re: errol]
|
enthusiast
Registered: 11/06/2003
Posts: 384
|
That happens with jEmplode on occasion.
--Nathan
|
|
Top
|
|
|
|
|
|
Previous Topic
Index