Update from 1.0.4 to 1.1.0 (locale::facet::_S_create_c_locale name not valid)

mcmatrix · July 2021

Hi.

I initiated the update from Web UI to the latest but it was doing it and doing it, restarted the RaspPi.
Then tried installing it from ssh by downloading and installing Repetier-Server-1.1.0-Linux.deb

But still, the service won't run and web UI gives 504 Gateway Time-out

When trying to run it manually then I'm getting the following error.
sudo /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml

locale::facet::_S_create_c_locale name not valid

What's wrong with it?

Repetier · July 2021

You need local C and run as repetierserver user:

sudo -u repetierserver LC_ALL=C /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml

is the manual way to start it in console.

mcmatrix · July 2021

Thank you.

Now it looks like it's waiting for "Reading firmware data ..."

pi@Repetier-Server:~ $ sudo -u repetierserver LC_ALL=C /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml

Read configuration file /usr/local/Repetier-Server/etc/RepetierServer.xml

Testing alternative config: "/usr/local/Repetier-Server/etc/RepetierServer-extra.xml"

Testing alternative config: "/var/lib/Repetier-Server/database/RepetierServer.xml"

ServerSetting::init()

Reading server settings...

18:43:38.475: Imported external command Shutdown Server

18:43:38.475: Imported external command Reboot Server

18:43:38.475: Imported external command Restart Klipper

18:43:38.475: Imported external command Power Printer Off

18:43:38.475: Imported external command Power Printer On

18:43:38.475: Imported allowed execute command poweron

18:43:38.476: Imported allowed execute command poweroff

18:43:38.476: Webdirectory: /usr/local/Repetier-Server/www/

18:43:38.476: Storage directory: /var/lib/Repetier-Server/

18:43:38.476: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml

18:43:38.476: Directory for temporary files: /tmp/

18:43:38.476: Reading firmware data ...

Edit: After ~10min it's still waiting at the same spot.

mcmatrix · July 2021

I'm still not able to get 1.1.0 running.
When I downgraded the repetier-server from 1.1.0 to 1.0.4 then version 1.0.4 immediately started to work.
Tried to install the latest version once more but it stopped at the same point.
When manually running then it stops on "Reading firmware data ..." and nothing more.
It's stuck at that point.

Repetier · July 2021

Ok, that is strange since i can read all firmware definitions. Do you have any own firmware definition files or modified versions? After that output and next one it also loads database/webcalls.json

To see which file it is handling where the hang happens you could start it with strace like this:

sudo -u repetierserver LC_ALL=C strace /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml

Especially the last output with
open("

would be of interest, so we know which file causes the hang. You can then send me that file for analysis. It is either defect or has mods from your side causing it I guess, but it should not hang in any case, so interested to see how it can hang.

mcmatrix · July 2021

Hi,

Sent that file to info email.
Yes, I have my own lines in firmware file Klipper.xml but this file
is always overwritten during install.

mcmatrix · July 2021

I used a new SD card and installed a fresh Raspberry Pi image V26.

After restoring from backup and configuring everything, it now looks okay.

orlins · August 2021

Hello,

I have exactly the same problem. Switched from 1.03 to 1.1 and my server no longer responds: 504 Gateway Time-out

I have my license since 2019 and I have not had any problem.

Florian

Repetier_Support · August 2021

Hello Florian,

We already noticed and fixed this 504 issue in version 1.1.2, which is also available now.
To get your current system working again, please reboot your server. After that you can install the fixed update.

mcmatrix · August 2021

Hi,

I have again the same issue.
Updated to the latest from 1.1.1 (like instructed in changelog)
My 1.1.1 was a clean install from the image.

The RepetierServer service is not starting correctly it runs till "Reading firmware data ..." and stays there.

pi@RepetierServer:~ $ sudo -u repetierserver LC_ALL=C /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml Read configuration file /usr/local/Repetier-Server/etc/RepetierServer.xml
Testing alternative config: "/usr/local/Repetier-Server/etc/RepetierServer-extra.xml"
Testing alternative config: "/var/lib/Repetier-Server/database/RepetierServer.xml"
ServerSetting::init()
Reading server settings...
16:27:12.549: Imported external command Shutdown Server
16:27:12.550: Imported external command Reboot Server
16:27:12.551: Imported external command Restart Klipper
16:27:12.551: Imported external command Power Printer Off
16:27:12.552: Imported external command Power Printer On
16:27:12.552: Imported allowed execute command poweron
16:27:12.553: Imported allowed execute command poweroff
16:27:12.553: Webdirectory: /usr/local/Repetier-Server/www/
16:27:12.554: Storage directory: /var/lib/Repetier-Server/
16:27:12.554: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
16:27:12.554: Directory for temporary files: /tmp/
16:27:12.556: Reading firmware data ...

The strace is more or less the same as the previous time

...
rk(0x1e36000) = 0x1e36000
open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 8
read(8, "O\210\220\3324\254\224\261Q\\\1w/ -f\225S\0206\367\311t\f,\201\206#6\251\224\344"..., 252) = 252
close(8) = 0
stat64("/usr/local/Repetier-Server/firmware/MK4duo.xml", {st_mode=S_IFREG|0644, st_size=18410, ...}) = 0
open("/usr/local/Repetier-Server/firmware/MK4duo.xml", O_RDONLY|O_LARGEFILE) = 8
read(8, "<?xml version=\"1.0\" encoding=\"UT"..., 4092) = 4092
read(8, "erTemperatureWait\">M191 S{i:temp"..., 4092) = 4092
open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 9
read(9, "\222\r\341\23\225h;\5\356A\22\23l\360\360B\275\223\177\356jZ\20\21\255\223\305\31\244ZJ\346"..., 252) = 252
close(9) = 0
read(8, "\"sdMounted\" value=\"0\">^SD card r"..., 4092) = 4092
read(8, "cceleration\">M201 .*X(\\d+\\.?\\d*)"..., 4092) = 4092
read(8, "\\d+) Baudrate</setting>\n "..., 4092) = 2042
read(8, "", 4092) = 0
close(8) = 0
brk(0x1e37000) = 0x1e37000
brk(0x1e38000) = 0x1e38000
brk(0x1e39000) = 0x1e39000
brk(0x1e3a000) = 0x1e3a000
brk(0x1e3b000) = 0x1e3b000
brk(0x1e3c000) = 0x1e3c000
brk(0x1e3d000) = 0x1e3d000
brk(0x1e3e000) = 0x1e3e000

Now installing back the previous version 1.1.1 is also not working.
There's something after version 1.0.4 (That version was working)

Tried these packages:
http://download.repetier.com/files/server/debian-armhf/Repetier-Server-1.1.2-Linux.deb
http://download.repetier.com/files/server/debian-armhf/Repetier-Server-1.1.1-Linux.deb

The next after "Reading firmware data ..." is the network?
Maybe there is something that this step cannot be initiated.

I'm not very interested to make again a clean install from the image.

mcmatrix · August 2021

I think I found a cause and solution to my issue.
I made previously a backup folder under /usr/local/Repetier-Server/firmware/
where I stored the Klipper.xml firmware file previous version before trying 1.1.2 update.
I also had this folder before my a fresh install from the image.
It looks that this folder and content somehow messed up with the RepetierServer server.

After deleting that folder from the firmware folder everything started to work.
Till version 1.0.4 that folder didn't have any effect.

Repetier · August 2021

Code is this:

RLog::log("Reading firmware data ...");

Firmware::readFirmwares();

WebCall::load();

RLog::log("Starting Network ...");

So if we assume it is after reading firmware data it is your database/webcalls.json file. Can you post your file so I can test if it works for me and if not why it is hanging.

mcmatrix · August 2021

Thanks for the info.
I think the bad boy was my extra backup folder & content inside the firmware directory.
At least after removing that extra folder the service started to work.

I don't have such file on /var/lib/Repetier-Server/database folder.

drwxr-x--- 2 repetierserver dialout 4096 Aug 7 17:53 .
drwxr-xr-x 15 repetierserver dialout 4096 Jul 28 22:13 ..
-rw-r----- 1 repetierserver dialout 3959 Jul 29 00:47 extcommands.xml
-rw-r----- 1 repetierserver dialout 3 Jul 29 00:44 gpio.json
-rw-r----- 1 repetierserver dialout 66560 Aug 5 00:49 history.sql
-rw-r----- 1 repetierserver dialout 2048 Aug 6 22:10 key.sql
-rw-r----- 1 repetierserver dialout 1211 Jul 28 22:13 renderer.json
-rw-r----- 1 repetierserver dialout 323 Jul 28 22:13 repetier-network-stored.xml
-rw-r----- 1 repetierserver dialout 323 Jul 28 22:13 repetier-network.xml
-rw-r----- 1 repetierserver dialout 37888 Aug 6 22:10 settings.sql
-rw-r----- 1 repetierserver dialout 5120 Aug 4 22:15 user.sql
-rw-r----- 1 repetierserver dialout 23552 Aug 4 22:16 workdispatcher.sql

At the moment I have 1.1.2 version up & running.
Thank you for your support.

Repetier · August 2021

You really found it. Tried it and with extra folder it also failed to start. Actually any file not ending with .xml would have caused this. Have fixed this for next update. Thanks.

Update from 1.0.4 to 1.1.0 (locale::facet::_S_create_c_locale name not valid)

Comments