Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - phenigma

Pages: 1 ... 61 62 [63] 64 65 ... 105
931
Installation issues / Re: PC as Media Director (PXE)
« on: September 23, 2012, 09:42:50 pm »
Or is it better to install a small disk in the pc, and use it like that instead of PXE?

There is no supported way to boot an MD from a disk.  PXE booting is the only supported method of booting an MD.

J.

932
Installation issues / Re: Unable to add generic pc as MD - template 28
« on: September 22, 2012, 07:10:58 am »
Excellent!  You're welcome.

J.

933
Installation issues / Re: Unable to add generic pc as MD - template 28
« on: September 17, 2012, 11:35:06 pm »
Glad things are moving forward for you!

Let me know what happens with your MD as it is PXE booting the first time.

J.

934
I forgot to mention that if I run a video directly on kde desktop, xine does use AC3/DTS pass through and Im able to listen to multichannel audio.  How xine is controlled by lmce? which is the config file used?  If the check to enable pass-through is activated, what does it does? what does it changes? which files are affected?

Sounds like we may be missing info in our /etc/pluto/xine.conf for passthrough device.  I'm not sure what kind of changes asound.conf has been through recently but /etc/pluto/xine.conf would have to be updated to reflect any new device names...

J.

935
inittab does not affect md creation.  If you have this problem then you would have no avwizard at all, ever.

J.

936
Installation issues / Re: Unable to add generic pc as MD - template 28
« on: September 17, 2012, 04:30:50 am »
Code: [Select]
rm /etc/inittab

Then your avwizard will be able to start again.  A permanent fix for this is in the works.  A very new, but known problem with net install.

J.

937
Installation issues / Re: Unable to add generic pc as MD - templete 28
« on: September 16, 2012, 11:30:45 pm »
The whole environment is the same i had with 8.10, where the MD worked (core, md, switches, ip phones, ata, z-wave, etc... The only change is is the new 10.04.
Thats why i'm asking about template 28. Yes, i also did run the create TB?? (don't remember exactly the name) before trying to boot the md.

Okay, I understand what you are saying.  Was this a DVD install or a net install?  If dvd install, which snapshot did you use?  If you used snapshot you should not run Diskless_CreateTBZ as it is already done for you.  If you did a network install did Diskless_CreateTBZ.sh finish completey and tell you there were 'no detectable errors'?

Do this:
Remove any manually created MDs on your core within webadmin.
Quick Reload dcerouter
Turn on the MD with PXE boot enabled

What happens on the MD's monitor?  It should show you that it has 'Announced ourselves to the router' and that it is 'Running Diskless_Setup'.  You should see these things on your MDs monitor when you PXE boot it the first time.  Are you seeing this?  If you are not seeing this, what exactly does the MD do when you turn it on?

J.

938
Finally, do you think we could get a FAQ going just about how 10.04 asterisk is supposed to work and the gotchas? Searching the forum and/or wiki gives you all the flavors of asterisk used to date and is highly inefficient. Since freepbx is no longer implemented, searching the web isn't useful as it assumes you are using freepbx as part of the solution.

Guys, remember that documentation is a community effort.  *Someone* needs to produce the wiki docs, it would be great if you guys could document what you discover as you are going.  <nudge, nudge, wink, wink>  File defect tickets for any functionality that is present but not working.  File feature_request tickets for any functionality that does not currently exist.

J.

939
Installation issues / Re: Unable to add generic pc as MD - templete 28
« on: September 16, 2012, 10:33:22 pm »
so, any hint in how to solve? i guess not, so so, for the third time in 3 days i will install the whole system again from ground zero: spa3102 does not work, my sip line are mute for incoming and outgoing, the diskless media server is recognized as a file server.....

Sound like you have not enabled PXE boot or 'network boot' on the machine you are trying to use as an MD.  If you PXE boot the machine it will be automagically detected as an MD and install all the correct templates.  Do not attempt to do this manually!

J.

940
This looks like the same thing my upgraded core has been doing.  I'll try to have a look later today and see if I can chase it down on my core, could be the same issue that others are having.

J.

941
Installation issues / Re: PC as Media Director (PXE)
« on: September 15, 2012, 04:04:16 am »
You will not need to run the TBZ file... and chances are everything will "just work". I would put those chances pretty high at the moment.
Yes, I should have mentioned that, sorry L3mce.

The large delay and the ssh issue are networking issues, as L3mce indicated in a previous post.  The database connection errors are normal.

J.

942
Users / Re: Hello everyone!!!
« on: September 15, 2012, 12:09:14 am »
Welcome!

Like L3mce I have an industrial automation/PLC/DCS background.  Allen Bradley/PanelView, Modicon, Wonderware...

There is a lot to learn here and help available when you need it.  Have fun!

J.

943
Installation issues / Re: PC as Media Director (PXE)
« on: September 14, 2012, 11:11:49 pm »
I was a bit impatient i think.   ::)

The error 'ERROR 2003 (HY000): Can't connect to MySQL server on 'dcerouter' (110)' needed to be about 20 times on my screen, and took about 15 minutes. After that, the installation went one without errors .


I will look at this.  It doesn't take that long to fail connecting and continue on my systems but I'll see what its doing and determine if it needs to make the connection or not.

Also, your MD *should* boot at reasonable speed.  Install from the snapshot as L3mce suggests.

J.

944
Installation issues / Re: PC as Media Director (PXE)
« on: September 14, 2012, 12:15:29 am »
I've installed it from the DVD.

And when i run /usr/pluto/bin/Di...., it results in an error after a while:


brononius: Is diskless_createtbz.sh finishing or stopping at this error?

This error will not prevent MD creation afaik.  This is an error at the time of creation of the mythtv_player within the diskless image chroot creation process.  The diskless image in the chroot is trying to contact the mysql server on the dcerouter, it cannot resolve the address.  afaik this is normal behaviour during the image creation, at least that is what is has been doing for me and I have no issues.  Again, this indicated error should not prevent the MD creation at all.  I've added raspbian image generation to this script and I have tested it *many* times here for ubuntu i386 diskless image creation and I have had no issues.

If you add an MD manually it will not have it's /usr/pluto/diskless/XX directory structure created for you automatically.  You can manually cause it to be created by selecting the MD in the webadmin and choosing "Rebuild Image".  But this should not be necessary, the system should be detecting it automatically.

Side note to L3, diskless_createtbz.sh already creates it's own log file of it's activity and displays the name of the log file when the script starts.  log_file=/var/log/pluto/Diskless_MD_Creation_$(date +%Y%m%d_%H%M%S).log

J.

945
Users / Re: Dianemo S: Strange Behaviour with ID3 files
« on: September 13, 2012, 05:14:03 am »
i suddenly realized that in mainly all media directories, where an id3 file exists, a lot of other files with the same name exists, but with a appendix.

e.g.

ld.id3
ld.id3.0oZE5q
ld.id3.1o9VVh
ld.id3.2eYcuf
...


This happens continuously on my NAS as well, with LinuxMCE, not Dianemo.  I never chased it down completely.  It looked to me like something with UpdateMedia and tmp files while writing id3s.  Hundreds of these files build up on my NAS.

J.

Pages: 1 ... 61 62 [63] 64 65 ... 105