Topics

1

Installation issues / System freeze after adding second HDD

« on: September 25, 2010, 06:17:03 pm »

Hello,

on bought new HDD and installed latest snapshot LinuxMCE-8.10-23261 (before I was running the 7.10 version).
All was installed and running without problems. As all my data was on the old HDD, I have connected
it to the system. On Orbiter I selected to use it without LinuxMCE structure (only show files). Everything seemed to be OK. But after a while the system freezes. I though the power supply is not enough. Therefore I replaced it with new 500W ATX Power Supply. But the situation was the same. Then I examined the logs an found that the HDD is mounted several times till the system freeze.

What can I do with it?

Here is the log before the system freeze.

Sep 25 13:50:47 dcerouter kernel: [   84.023315] Bluetooth: Core ver 2.13
Sep 25 13:50:47 dcerouter kernel: [   84.026961] NET: Registered protocol family 31
Sep 25 13:50:47 dcerouter kernel: [   84.026973] Bluetooth: HCI device and connection manager initialized
Sep 25 13:50:47 dcerouter kernel: [   84.026981] Bluetooth: HCI socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.088034] Bluetooth: L2CAP ver 2.11
Sep 25 13:50:47 dcerouter kernel: [   84.088044] Bluetooth: L2CAP socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.143563] Bluetooth: RFCOMM socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.144163] Bluetooth: RFCOMM TTY layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.144178] Bluetooth: RFCOMM ver 1.10
Sep 25 13:50:47 dcerouter kernel: [   84.147535] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 25 13:50:47 dcerouter kernel: [   84.147548] Bluetooth: BNEP filters: protocol multicast
Sep 25 13:50:47 dcerouter kernel: [   84.226954] Bridge firewalling registered
Sep 25 13:50:47 dcerouter kernel: [   84.283001] Bluetooth: SCO (Voice Link) ver 0.6
Sep 25 13:50:47 dcerouter kernel: [   84.283014] Bluetooth: SCO socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.712130] NET: Registered protocol family 17
Sep 25 13:51:03 dcerouter kernel: [  100.568060] kjournald starting.  Commit interval 5 seconds
Sep 25 13:51:03 dcerouter kernel: [  100.576658] EXT3 FS on sdb1, internal journal
Sep 25 13:51:03 dcerouter kernel: [  100.576675] EXT3-fs: recovery complete.
Sep 25 13:51:03 dcerouter kernel: [  100.577481] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:51:42 dcerouter kernel: [  139.606754] kjournald starting.  Commit interval 5 seconds
Sep 25 13:51:42 dcerouter kernel: [  139.608577] EXT3 FS on sdb1, internal journal
Sep 25 13:51:42 dcerouter kernel: [  139.608599] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:51:46 dcerouter kernel: [  143.477474] kjournald starting.  Commit interval 5 seconds
Sep 25 13:51:46 dcerouter kernel: [  143.479190] EXT3 FS on sdb1, internal journal
Sep 25 13:51:46 dcerouter kernel: [  143.480098] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:52:52 dcerouter kernel: [  209.358722] kjournald starting.  Commit interval 5 seconds
Sep 25 13:52:52 dcerouter kernel: [  209.360905] EXT3 FS on sdb1, internal journal
Sep 25 13:52:52 dcerouter kernel: [  209.361960] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:52:58 dcerouter kernel: [  215.489889] kjournald starting.  Commit interval 5 seconds
Sep 25 13:52:58 dcerouter kernel: [  215.491557] EXT3 FS on sdb1, internal journal
Sep 25 13:52:58 dcerouter kernel: [  215.492472] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:56:06 dcerouter kernel: [  402.983011] kjournald starting.  Commit interval 5 seconds
Sep 25 13:56:06 dcerouter kernel: [  402.984808] EXT3 FS on sdb1, internal journal
Sep 25 13:56:06 dcerouter kernel: [  402.985690] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:56:39 dcerouter kernel: [  435.874535] kjournald starting.  Commit interval 5 seconds
Sep 25 13:56:39 dcerouter kernel: [  435.876286] EXT3 FS on sdb1, internal journal
Sep 25 13:56:39 dcerouter kernel: [  435.877164] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:57:27 dcerouter kernel: [  484.025657] kjournald starting.  Commit interval 5 seconds
Sep 25 13:57:27 dcerouter kernel: [  484.027377] EXT3 FS on sdb1, internal journal
Sep 25 13:57:27 dcerouter kernel: [  484.028627] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:58:00 dcerouter kernel: [  517.532721] kjournald starting.  Commit interval 5 seconds
Sep 25 13:58:00 dcerouter kernel: [  517.534426] EXT3 FS on sdb1, internal journal
Sep 25 13:58:00 dcerouter kernel: [  517.535304] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:00:42 dcerouter kernel: [  679.085509] kjournald starting.  Commit interval 5 seconds
Sep 25 14:00:42 dcerouter kernel: [  679.087292] EXT3 FS on sdb1, internal journal
Sep 25 14:00:42 dcerouter kernel: [  679.088207] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:02:18 dcerouter kernel: [  775.677016] kjournald starting.  Commit interval 5 seconds
Sep 25 14:02:18 dcerouter kernel: [  775.679203] EXT3 FS on sdb1, internal journal
Sep 25 14:02:18 dcerouter kernel: [  775.680149] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:03:39 dcerouter kernel: [  856.277193] kjournald starting.  Commit interval 5 seconds
Sep 25 14:03:39 dcerouter kernel: [  856.278931] EXT3 FS on sdb1, internal journal
Sep 25 14:03:39 dcerouter kernel: [  856.279806] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:05:24 dcerouter kernel: [  960.863534] kjournald starting.  Commit interval 5 seconds
Sep 25 14:05:24 dcerouter kernel: [  960.865426] EXT3 FS on sdb1, internal journal
Sep 25 14:05:24 dcerouter kernel: [  960.866304] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:06:12 dcerouter kernel: [ 1009.312164] kjournald starting.  Commit interval 5 seconds
Sep 25 14:06:12 dcerouter kernel: [ 1009.313889] EXT3 FS on sdb1, internal journal
Sep 25 14:06:12 dcerouter kernel: [ 1009.314769] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:07:01 dcerouter kernel: [ 1058.135445] kjournald starting.  Commit interval 5 seconds
Sep 25 14:07:01 dcerouter kernel: [ 1058.137207] EXT3 FS on sdb1, internal journal
Sep 25 14:07:01 dcerouter kernel: [ 1058.138088] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:11:58 dcerouter kernel: [ 1355.339290] kjournald starting.  Commit interval 5 seconds
Sep 25 14:11:58 dcerouter kernel: [ 1355.341073] EXT3 FS on sdb1, internal journal
Sep 25 14:11:58 dcerouter kernel: [ 1355.341953] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:12:55 dcerouter kernel: [ 1411.865639] kjournald starting.  Commit interval 5 seconds
Sep 25 14:12:55 dcerouter kernel: [ 1411.867363] EXT3 FS on sdb1, internal journal
Sep 25 14:12:55 dcerouter kernel: [ 1411.868264] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:14:24 dcerouter kernel: [ 1500.876184] kjournald starting.  Commit interval 5 seconds
Sep 25 14:14:24 dcerouter kernel: [ 1500.878034] EXT3 FS on sdb1, internal journal
Sep 25 14:14:24 dcerouter kernel: [ 1500.878899] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:15:28 dcerouter kernel: [ 1565.538548] kjournald starting.  Commit interval 5 seconds
Sep 25 14:15:28 dcerouter kernel: [ 1565.540691] EXT3 FS on sdb1, internal journal
Sep 25 14:15:28 dcerouter kernel: [ 1565.541574] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:16:00 dcerouter kernel: [ 1597.475716] kjournald starting.  Commit interval 5 seconds
Sep 25 14:16:00 dcerouter kernel: [ 1597.477449] EXT3 FS on sdb1, internal journal
Sep 25 14:16:00 dcerouter kernel: [ 1597.478330] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:19:29 dcerouter kernel: [ 1806.240143] kjournald starting.  Commit interval 5 seconds
Sep 25 14:19:29 dcerouter kernel: [ 1806.242025] EXT3 FS on sdb1, internal journal
Sep 25 14:19:29 dcerouter kernel: [ 1806.242906] EXT3-fs: mounted filesystem with ordered data mode.

2

Feature requests & roadmap / Asterisk and Security

« on: June 24, 2010, 07:58:35 am »

today I became phone bill  from my SIP account provider and it was a shock for me. It was for 1000 EUR.
I do not not believed it. Than I examined call log's in FreePBX, there were to see 24 calls to Siera Leone and Litva
total time about 30 minutes. After that I became list of calls from my provider. There were also 24 call's
but total time about 6 hours. I don't understand this. Why has Asterisk different call duration in log as my provider?

I have searched in Asterisk logs and found attack from outside. The hacker has connected to extension 1001 and placed calls.

My first problem was in instruction from my provider. They told me that I must open port 5060 in firewall to be able to
place and receive calls. Before that Asterisk was not able to register in their system. But this was also a open door
and invitation for attacker  to connect to on of my extensions. My fault, i did not realize at that moment that this is a big security problem.


Second problem is that the password for certain extension is the same as extension number!!! That's the first a attacker try.
We mus definitely change this. At first install it's OK, but after that, there should be a possibility in Wizard->Phones to change
the password.

Third problems. I also saw in log's other attack to my system. Should we not utilise some sort of program as fail2ban
to protect the system against such attacks?

has someone from you the target of similar attack?

3

Installation issues / Orbiter on MD not starting.

« on: June 18, 2010, 09:46:34 am »

Hello,
I have installed 0810 branch on my backup server. After then done several steps (described on wiki) to be able to boot the MD over network.

I have connected the test MD to network and booted up. It show's me the AW vizard page, I go throe , everything looks OK.
Then shutted down the MD. In admin page I seen the new MD and Orbiter. I given the command to regenerate the orbiter and waited to be done.
Booted the MD, it's look's OK, X is started , show some installing stuff. The a error : Can't get orbiter configuration or Orbiter is being regenerated
I let it whole night running, but now success. The orbiter does not start. Here is the LaunchOrbiter.log from the diskless MD.

Code: [Select]

Fri Jun 18 09:14:14 CEST 2010 Restart
========== NEW LOG SECTION ==========
1 06/18/10 09:14:23 36 (spawning-device) [1;00mStarting... 2[1;00m
1 06/18/10 09:14:23 36 (spawning-device) [1;00mFound /usr/pluto/bin/LaunchOrbiter.sh [1;00m
01 06/18/10 9:14:25.651 [31;1mDirectory: C36/ doesn't contain the orbiter's .info file.  Requesting files from the server. [0m <0xb71876c0>
01 06/18/10 9:14:25.672 [31;1mUnable to get Orbiter data [0m <0xb71876c0>
05 06/18/10 9:14:47.236 [33;1mvoid ClientSocket::Disconnect() on this socket: 0x9793a60 (m_Socket: 11) [0m <0xb71876c0>
05 06/18/10 9:14:49.235 [33;1mOrbiter reloading... [0m <0xb71876c0>
05 06/18/10 9:14:49.235 [33;1mOrbiter quiting... [0m <0xb71876c0>
05 06/18/10 9:14:49.236 [33;1mGot an on quit.  Pushing an event into SDL [0m <0xb71876c0>
05 06/18/10 9:14:49.236 [33;1mGot an on quit.  Pushing an event into SDL [0m <0xb71876c0>
05 06/18/10 9:14:49.256 [33;1mXRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=158846960, pDisplay_DataConnection=158848776 ->Closing [0m <0xb3f8ab90>
05 06/18/10 9:14:49.258 [33;1mXRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=158846960, pDisplay_DataConnection=158848776 ->Closed [0m <0xb3f8ab90>
05 06/18/10 9:14:50.677 [33;1mvoid ClientSocket::Disconnect() on this socket: 0x96f87e0 (m_Socket: 10) [0m <0xb71876c0>
Return code: 2

I have also tried another MD to boot, but the  result was the same.
Does anybody know where the problem might bee.

mihajzm

4

Developers / new language - Slovak

« on: June 10, 2010, 07:42:24 am »

Hello ,

I have the translation to Slovak language almost done (will send it today).

I have found some misspelled names in webadmin.
Basic info-> Installation when you select Country to SLOVAKIA, the region Nitrinsky should be Nitriansky.

I would like to repair this things also add new Cities for Slovakia with GPS possitions. Where in database can I found the table to add it?
How to make it good, that the changes would be in next release.

thanks

5

Developers / Starting to use 0810 version

« on: June 08, 2010, 11:22:52 am »

Two year ago I have installed the 0710 version of LinuxMCE, and it works till today. I have made some driver's for own boards, translation to Slovak.
I have two MD attached and so on.

The whole systems runs, now I want to contribute to community. But contributing for 0710 system is not worth allready.

Now I'm installing 0810 system (latest snapshot) to my backup server to see how it's working, and want to made all the drivers to work.

The question is, how to extract own made Templates, Language from previous system and transfer it to the new version?
Must I make it again from the beginning?

6

Developers / friendlyArm/mini2440 Orbiter progress?

« on: March 15, 2010, 10:02:14 pm »

Hello,
recently I bought mini2440 board with 7" TouchScreen LCD. I have already setup development environment based on buildroot.

I saw that there is work in progress to port Orbiter to this platform. Is there something to try or to work on? I have some experience with C and C++ programming for embedded devices and can help with this. It would be nice to see working Orbiter on mini.

I have already tried to compile some things (libDCEcommon,libPlutoUtils,libSDL_Helpers,libSerializeClass) but got problems by building/linking Orbiter.

mihajzm

7

Developers / Start custom made DCE (cpp) device at boot.

« on: April 02, 2009, 09:07:28 pm »

Hi,
after some instruction http://forum.linuxmce.org/index.php?topic=7706.0 I finally successfully compiled bunch of my custom made DCE devices. I can start them from command line and all is working, I can see data from my sensors (mostly AVR microcontrollers with PHY or AVR+RS485) on orbiter, switch relays etc. Now I copied the binaries to /usr/pluto/bin and hopped that after reboot they are executed with some sort of startup script. But nothing happens 
What must I setup or hack that these devices are automatically started at boot?

What I have also done:
created New Software package (Advanced->Software->Packages->Create new package) for each device pointing to binary in /usr/pluto/bin
In Device Templates , added each package to right template.

thanks in advance.

8

Installation issues / transfer diskless image on compact flash?

« on: March 26, 2009, 09:47:37 pm »

Hi,
now my client boots over network, there is no problem, but it's realy lazy
Is there a way to transfer diskless image to compact flash card to boot faster,

9

Developers / question about Translation

« on: March 22, 2009, 07:57:19 pm »

Hello,

I have successfully installed LinuxMCE on my automation server this weekend. And I find it's a great software.
Now I want to translate the UI to Slovak language. I found various info how to done it. Installed HAD designer, successfully connected to database. Now when I want to change I have three options in the table English,French,German. I could rewrite text in one of these, but I want to have option for Slovak. How can I add this option to database?

thanks for answer.