Different errors after update to V6.3

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
king008
Posts: 8
Joined: Wed Dec 13, 2017 10:04 am

Different errors after update to V6.3

Post by king008 »

Hello everyone,

After update V6.2 to V6.3, I see this error messages:

After login as user (not root):

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

After root login:

DietPi | 22:46 | Wed 07/03/18
───────────────────────────────────────
v6.3 | RPi 3 Model B (armv7l)
───────────────────────────────────────
NULL: error fetching interface information: Device not found
NULL |

───────────────────────────────────────

Created by : Daniel Knight
Web : http://DietPi.com
Twitter : http://twitter.com/dietpi_
Donate : http://goo.gl/pzISt9
DietPi's web hosting is powered by: MyVirtualServer.com

dietpi-launcher = All the DietPi programs in one place.
dietpi-config = Feature rich configuration tool for your device.
dietpi-software = Select optimized software for installation.
htop = Resource monitor.
cpu = Shows CPU information and stats.


How can I fix this problems?
User avatar
Fourdee
Site Admin
Posts: 2788
Joined: Tue Feb 06, 2007 1:36 pm

Re: Different errors after update to V6.3

Post by Fourdee »

Hi,

Thanks for the report:
- Which SSH server are you running (default dropbear)?
- Please paste results ifconfig
- Please paste results locale
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
SwissBear
Posts: 3
Joined: Fri Mar 09, 2018 9:04 am

Re: Different errors after update to V6.3

Post by SwissBear »

Hi,
Another problem I noticed: prior to 6.3, when changing the 'NICE' and priorities for a set of tasks (for instance to prioritise Roon/RAAT), DietPi was recording the changes and restarting with the modified parameters after a reboot/restart. From 6.3, parameters need to be changed after every restart.
Could you please check ?
king008
Posts: 8
Joined: Wed Dec 13, 2017 10:04 am

Re: Different errors after update to V6.3

Post by king008 »

Fourdee wrote:Hi,

Thanks for the report:
- Which SSH server are you running (default dropbear)?
- Please paste results ifconfig
- Please paste results locale
Thank you for your answer! Here are the answers to your questions:

- Which SSH server are you running (default dropbear)?

I use OpenSSH and I have checked my version:

dpkg --list | grep 'openssh'

ii openssh-client 1:7.4p1-10+deb9u2 armhf secure shell (SSH) client, for secure access to remote machines
ii openssh-server 1:7.4p1-10+deb9u2 armhf secure shell (SSH) server, for secure access from remote machines
ii openssh-sftp-server 1:7.4p1-10+deb9u2 armhf secure shell (SSH) sftp server module, for SFTP access from remote machines

- Please paste results ifconfig

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:dd:53:22 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::9ade:d0ff:fe0e:b927 prefixlen 64 scopeid 0x20<link>
ether 98:de:d0:0e:b9:27 txqueuelen 1000 (Ethernet)
RX packets 300265 bytes 26308665 (25.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 202074 bytes 29921308 (28.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 17059 bytes 1671121 (1.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 17059 bytes 1671121 (1.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I use a USB connection for more internet speed on the PI. That's why he stands by eth1.

grep -ri 'ACTIVE_DEVICE' /DietPi/dietpi/func/obtain_network_details

ACTIVE_DEVICE='NULL'
ACTIVE_DEVICE="eth$ETH_INDEX"
ACTIVE_DEVICE="wlan$WLAN_INDEX"
IP_ADDRESS=$(ifconfig "$ACTIVE_DEVICE" | grep -m1 'inet' | awk '{ print $2 }' | cut -d: -f2 )
$ACTIVE_DEVICE


- Please paste results locale[/quote]

LANG=en_GB.UTF-8
LANGUAGE=
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=en_GB.UTF-8

cat /DietPi/dietpi/.network
0
0
NULL

I hope you can do something with this information? ;)
king008
Posts: 8
Joined: Wed Dec 13, 2017 10:04 am

Re: Different errors after update to V6.3

Post by king008 »

Another 'bug', I use NGINX. But after every reboot I see an apache2 directory in /var/log. I remove it and do a reboot, but after de reboot he's back.

I think, the problem is in /DietPi/dietpi/dietpi-ramlog:

#/////////////////////////////////////////////////////////////////////////////////////
#Main Loop
#/////////////////////////////////////////////////////////////////////////////////////
#Startup Phase (restore /var/log directory structure and files)
if (( $INPUT == 0 )); then

echo -e "DietPi-Ramlog: Starting"

#Create core directories, regardless of Logging mode.
# - This prevents core system programs failing to write to their logfile (eg: logsave process will not terminate if the /fsck directory does not exist).
mkdir -p /var/log/apt &> /dev/null
mkdir -p /var/log/apache2 &> /dev/null
mkdir -p /var/log/fsck &> /dev/null
mkdir -p /var/log/news &> /dev/null
mkdir -p /var/log/samba &> /dev/null
mkdir -p /var/log/ntpstats &> /dev/null

Maybe you can make a check if Apache and NGINX is used? If no, then do not create it. Where is NGINX in this file? (I didn't used samba, but there is also a directory in /var/log)
User avatar
Fourdee
Site Admin
Posts: 2788
Joined: Tue Feb 06, 2007 1:36 pm

Re: Different errors after update to V6.3

Post by Fourdee »

SwissBear wrote:Hi,
Another problem I noticed: prior to 6.3, when changing the 'NICE' and priorities for a set of tasks (for instance to prioritise Roon/RAAT), DietPi was recording the changes and restarting with the modified parameters after a reboot/restart. From 6.3, parameters need to be changed after every restart.
Could you please check ?
Hi,

Unable to replicate here testing cron, all changes are saved and applied during reboots.

Which programs did you change the options for, that are not being applied after reboot?
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
User avatar
Fourdee
Site Admin
Posts: 2788
Joined: Tue Feb 06, 2007 1:36 pm

Re: Different errors after update to V6.3

Post by Fourdee »

king008 wrote: cat /DietPi/dietpi/.network
0
0
NULL

I hope you can do something with this information? ;)
Thanks for the info, which user was you logged in as?
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
king008
Posts: 8
Joined: Wed Dec 13, 2017 10:04 am

Re: Different errors after update to V6.3

Post by king008 »

Fourdee wrote:
king008 wrote: cat /DietPi/dietpi/.network
0
0
NULL

I hope you can do something with this information? ;)
Thanks for the info, which user was you logged in as?
First as PI and then as root with the su command. I did cat /DietPi/dietpi/.network as root.
SwissBear
Posts: 3
Joined: Fri Mar 09, 2018 9:04 am

Re: Different errors after update to V6.3

Post by SwissBear »

Fourdee wrote:
SwissBear wrote:Hi,
Another problem I noticed: prior to 6.3, when changing the 'NICE' and priorities for a set of tasks (for instance to prioritise Roon/RAAT), DietPi was recording the changes and restarting with the modified parameters after a reboot/restart. From 6.3, parameters need to be changed after every restart.
Could you please check ?
Hi,

Unable to replicate here testing cron, all changes are saved and applied during reboots.

Which programs did you change the options for, that are not being applied after reboot?
Thanks for checking. Used dietpi-process_tool. Will check again after update to 6.4 and report if still present.
SwissBear
Posts: 3
Joined: Fri Mar 09, 2018 9:04 am

Re: Different errors after update to V6.3

Post by SwissBear »

SwissBear wrote:
Fourdee wrote:
SwissBear wrote:Hi,
Another problem I noticed: prior to 6.3, when changing the 'NICE' and priorities for a set of tasks (for instance to prioritise Roon/RAAT), DietPi was recording the changes and restarting with the modified parameters after a reboot/restart. From 6.3, parameters need to be changed after every restart.
Could you please check ?
Hi,

Unable to replicate here testing cron, all changes are saved and applied during reboots.

Which programs did you change the options for, that are not being applied after reboot?
Thanks for checking. Used dietpi-process_tool. Will check again after update to 6.4 and report if still present.
Just checked. After reboot, one process (Roon Bridge) kept parameters given via process_tool. Others (RoonBridge Helper and RAAT Server) were dropped. Surprisingly, after power off/power on, the parameters changes were kept...
Post Reply