Quantcast
Channel: observium (Forum tag)
Viewing all 109 articles
Browse latest View live

05-19-219 Obsdervium appliance.

$
0
0

OK... this is driving me nuts...

Can someone please tell me where this is coming from so I can bang it out? I've dug through every single one of the files in /etc/apt/sources.list.d/  and there is no such entry anywhere that should be generating this error (of course it only started a month or so back due to EOL for the OS).

W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/main/binary-am... 404  Not Found [IP: 151.101.196.204 80]

LOL!!!!

Tags: 
Forum: 

Old TurnKey Observium appliance no longer showing graphs

$
0
0

I just had an email from Stuart regarding support for an old TurnKey Observium appliance. So I'm reposting it here.


I’m running observium on a turnkey linux applicance and an update to the rrd tool last night has broken our graphs. I managed to find that it’s a issue with the rrd tool itself and there is a new package to install.

This is the error:

RRDTool Output: ERROR: cannot compile regular expression: Error while compiling regular expression ^(?:[^%]+|%%)*%[+- 0#]?[0-9]*([.][0-9]+)?l[eEfF](?:[^%]+|%%)*%s(?:[^%]+|%%)*$ at char 18: range out of order in character class (^(?:[^%]+|%%)*%[+- 0#]?[0-9]*([.][0-9]+)?l[eEfF](?:[^%]+|%%)*%s(?:[^%]+|%%)*$)
RRDtool Runtime: 0.011s | Total time: 0.012s

The mailing lists suggest that the bug is fixed in +deb8u2

looks like I am running:

1.4.8-1.2+deb8u1

I upgraded to 1.4.8-1.2++deb8u2:

admin@observium /home2/observium$ sudo apt-get update
Get:1 http://security.debian.org jessie/updates InRelease [44.9 kB]
Ign http://archive.turnkeylinux.org jessie-security InRelease
Ign http://http.debian.net jessie InRelease
Hit http://security.debian.org jessie/updates/main amd64 Packages
Ign http://archive.turnkeylinux.org jessie InRelease
Hit http://http.debian.net jessie Release.gpg
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Get:2 http://security.debian.org jessie/updates/main Translation-en [387 kB]
Hit http://archive.turnkeylinux.org jessie-security Release.gpg
Hit http://http.debian.net jessie Release
Hit http://http.debian.net jessie/main amd64 Packages
Hit http://archive.turnkeylinux.org jessie Release.gpg
Hit http://http.debian.net jessie/contrib amd64 Packages
Hit http://http.debian.net jessie/contrib Translation-en
Hit http://archive.turnkeylinux.org jessie-security Release
Hit http://http.debian.net jessie/main Translation-en
Hit http://archive.turnkeylinux.org jessie Release
Hit http://archive.turnkeylinux.org jessie-security/main amd64 Packages
Hit http://archive.turnkeylinux.org jessie/main amd64 Packages
Ign http://archive.turnkeylinux.org jessie-security/main Translation-en
Ign http://archive.turnkeylinux.org jessie/main Translation-en
Fetched 431 kB in 5s (80.4 kB/s)
Reading package lists... Done
W: There is no public key available for the following key IDs:
AA8E81B4331F7F50
admin@observium /home2/observium$ sudo apt-get install rrdtool
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libuuid-perl linux-image-3.16.0-4-amd64 linux-image-3.16.0-5-amd64 linux-image
Use 'apt-get autoremove' to remove them.
Suggested packages:
librrds-perl
The following packages will be upgraded:
rrdtool
1 upgraded, 0 newly installed, 0 to remove and 67 not upgraded.
Need to get 434 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://security.debian.org/ jessie/updates/main rrdtool amd64 1.4.8-1.2+de
Fetched 434 kB in 0s (1928 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 56070 files and directories currently installed.)
Preparing to unpack .../rrdtool_1.4.8-1.2+deb8u2_amd64.deb ...
Unpacking rrdtool (1.4.8-1.2+deb8u2) over (1.4.8-1.2+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up rrdtool (1.4.8-1.2+deb8u2) ...
Counting objects: 1938, done.
Compressing objects: 100% (1127/1127), done.
Writing objects: 100% (1938/1938), done.
Total 1938 (delta 236), reused 1938 (delta 236)
admin@observium /home2/observium$ sudo apt-get install rrdtool
Reading package lists... Done
Building dependency tree
Reading state information... Done
rrdtool is already the newest version.
The following packages were automatically installed and are no longer required:
libuuid-perl linux-image-3.16.0-4-amd64 linux-image-3.16.0-5-amd64 linux-image
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 67 not upgraded.

But I am still having the issue with graphs not drawing.

Forum: 

Comparison setup Observium OVA vs Core

$
0
0

I've quickly set up an Observium VM using the v16 ova and in parallel to it I've deployed a Core VM using also the v16 ova.

Platform is ESXi 6.5.

Core works nicely, but with Observium I have a no-go situation, still problems finding a way to boot.

I've attached a screenshot-comparison of both VMs, deployed in the same ESXi server, in the same Datastore.

Differences I've noticed:

a) Observium has no vmtools (of course)
b) Observium is running CPU at max
c) Observium uses almost no memory
d) Core uses almost no CPU
e) Core uses some memory
f) Observium uses about 1 GB more storage
g) In the settings I've only seen some differences related to vmtools

But overall I couldn't detect any main difference.

 

Weird...

Forum: 

Observium - error message

$
0
0

Hi to everyone:

 

Everytime i run a php command from the console i get this error message:

 

root@visum /opt/observium# php discovery.php -u

MIB search path: /opt/observium/mibs

Cannot find module (SNMPv2-MIB): At line 1 in (none)

Cannot find module (IF-MIB): At line 1 in (none)

Cannot find module (IP-MIB): At line 1 in (none)

Cannot find module (TCP-MIB): At line 1 in (none)

Cannot find module (UDP-MIB): At line 1 in (none)

Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none)

Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none)

Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none)

Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none)

Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none)

Cannot find module (MTA-MIB): At line 1 in (none)

Cannot find module (NETWORK-SERVICES-MIB): At line 1 in (none)

Cannot find module (UCD-DISKIO-MIB): At line 1 in (none)

Cannot find module (UCD-DLMOD-MIB): At line 1 in (none)

Cannot find module (LM-SENSORS-MIB): At line 1 in (none)

Cannot find module (UCD-SNMP-MIB): At line 1 in (none)

Cannot find module (UCD-DEMO-MIB): At line 1 in (none)

Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)

Cannot find module (NET-SNMP-AGENT-MIB): At line 1 in (none)

Cannot find module (SNMP-MPD-MIB): At line 1 in (none)

Cannot find module (SNMP-USER-BASED-SM-MIB): At line 1 in (none)

Cannot find module (SNMP-FRAMEWORK-MIB): At line 1 in (none)

Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 1 in (none)

Cannot find module (SNMP-COMMUNITY-MIB): At line 1 in (none)

Cannot find module (IPV6-ICMP-MIB): At line 1 in (none)

Cannot find module (IPV6-MIB): At line 1 in (none)

Cannot find module (IPV6-TCP-MIB): At line 1 in (none)

Cannot find module (IPV6-UDP-MIB): At line 1 in (none)

Cannot find module (IP-FORWARD-MIB): At line 1 in (none)

Cannot find module (NET-SNMP-PASS-MIB): At line 1 in (none)

Cannot find module (NET-SNMP-EXTEND-MIB): At line 1 in (none)

Cannot find module (SNMP-NOTIFICATION-MIB): At line 1 in (none)

Cannot find module (SNMPv2-TM): At line 1 in (none)

Cannot find module (NET-SNMP-VACM-MIB): At line 1 in (none)

__________________

 

please advice

Tags: 
Forum: 

Upgrade Observium Appliance

$
0
0

I want to transfer my old observium configuration to a new appliance installation.

I have downloaded the latest version of the appliance and I have copied the config.php and RRD directory to the new appliance.

I have also created a mysqldump of one of the database and imported it in the new system.

When I try to login to the web interface I get the following error:

DB Error 1045: Access denied for user 'observium'@'localhost' (using password: YES).

When I login through cli to the mysql database with 'observium' user I don't have any issue.

Now everytime I open the web interface I see the error message and not the login page.

Tags: 
Forum: 

Upgrade Observium lxc

$
0
0

Observium user.

I have proxmox 6.2-11 and running Observium 19.8.1 from a turnkey lxc. Can I upgrade Observium to the latest 20.9 version with-in the lxc container? 

Sorry for the newbie question. Just want to make sure I understand what, if any limitations to the lxc container is and what options I have. 

Thank you

 

Forum: 

Observium crashes every night : DB Error 2002: Connection refused

$
0
0

Hello,

It is owesome, I added a lot of devices but unfortunatly it crashes every night and show the error DB Error 2002: Connection refused when I go the observium web page. The log at the end might be the most relevant information I have to give but here is what I tried and thinked about :

  • I use the Observium OVA. I gave it 2Gb RAM and it has 500Mb Swap space if I understand good.
  • If I try to restart mysql, it hangs... Same if I try to reboot : a job is trying to close/finish, waiting...
  • The only solution if to find the Mysql process and kill it, or kill the VM. I use VMWare.
  • I looked for giving more swap space but I cannot find a simple solution to do so, so I stopped my researches.

 

Here is what I have in service mysql status :

Apr 16 01:30:15 observium systemd[1]: Starting MariaDB 10.3.27 database server...
Apr 16 01:30:15 observium mysqld[484]: 2021-04-16  1:30:15 0 [Note] /usr/sbin/mysqld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 484 ...
Apr 16 01:30:15 observium mysqld[484]: 2021-04-16  1:30:15 0 [Warning] Could not increase number of max_open_files to more than 16384 (request: 32183)
Apr 16 01:45:15 observium systemd[1]: mariadb.service: Start operation timed out. Terminating.
Apr 16 02:00:16 observium systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
Apr 16 02:15:16 observium systemd[1]: mariadb.service: State 'stop-final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
Apr 16 02:15:16 observium systemd[1]: mariadb.service: Failed with result 'timeout'.
Apr 16 02:15:16 observium systemd[1]: Failed to start MariaDB 10.3.27 database server.

Thank you in advance for your help

 

Edit :

Free -h :

              total        used        free      shared  buff/cache   available
Mem:          1.9Gi       179Mi       1.4Gi        25Mi       382Mi       1.6Gi
Swap:         511Mi        63Mi       448Mi

It is with the mysql crashed. I remember doing the same yesterday when it was working and available was a 1Gi I think.

journalctl -u mariadb returns nothing. It looks like there ain't no mariadb user. Mysql user exists but returns nothing either.

 

root@observium ~# cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
_apt:x:100:65534::/nonexistent:/usr/sbin/nologin
systemd-timesync:x:101:105:systemd Time Synchronization,,,:/run/systemd:/usr/sbin/nologin
systemd-network:x:102:106:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin
systemd-resolve:x:103:107:systemd Resolver,,,:/run/systemd:/usr/sbin/nologin
mysql:x:104:108:MySQL Server,,,:/nonexistent:/bin/false
shellinabox:x:105:109:Shell In A Box,,,:/var/lib/shellinabox:/usr/sbin/nologin
messagebus:x:106:110::/nonexistent:/usr/sbin/nologin
stunnel4:x:107:111::/var/run/stunnel4:/usr/sbin/nologin
ntp:x:108:115::/nonexistent:/usr/sbin/nologin
postfix:x:109:116::/var/spool/postfix:/usr/sbin/nologin
sshd:x:110:65534::/run/sshd:/usr/sbin/nologin
libvirt-qemu:x:64055:102:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin
systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
root@observium ~# journalctl -u mysql
-- Logs begin at Fri 2021-04-16 12:04:49 UTC, end at Fri 2021-04-16 18:45:46 UTC. --
-- No entries --

For the available space, it looks fine (as you said in another post, it's when we come down to 1% free or less than 1G that it becomes very problematic?) :

root@lg-info-observium ~# df -h /
Filesystem                Size  Used Avail Use% Mounted on
/dev/mapper/turnkey-root   17G   13G  3.6G  78% /

Here is what happens when I try to restart mysql :

root@observium ~# service mysql restart
^C
root@observium ~# service mysql status
* mariadb.service - MariaDB 10.3.27 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: deactivating (stop-sigterm) (Result: exit-code) since Fri 2021-04-16 01:30:10 UTC; 17h ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 18818 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
  Process: 18819 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 18821 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, sta
  Process: 18922 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
 Main PID: 18922 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"
    Tasks: 3 (limit: 2355)
   Memory: 72.3M
   CGroup: /system.slice/mariadb.service
           `-484 /usr/sbin/mysqld

Apr 16 18:54:14 observium systemd[1]: Starting MariaDB 10.3.27 database server...
Apr 16 18:54:14 observium systemd[1]: mariadb.service: Found left-over process 484 (mysqld) in control group while starting unit. Ignoring.
Apr 16 18:54:14 observium systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 16 18:54:14 observium mysqld[18922]: 2021-04-16 18:54:14 0 [Note] /usr/sbin/mysqld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 18922 ...
Apr 16 18:54:14 observium mysqld[18922]: 2021-04-16 18:54:14 0 [Warning] Could not increase number of max_open_files to more than 16384 (request: 32183)
Apr 16 18:54:48 observium systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE

Here is when I kill it and restart :

root@observium ~# ps -aux |grep mysql
mysql      484  0.0  2.7 473288 56520 ?        Ssl  01:30   0:00 /usr/sbin/mysqld
root     19006  0.0  0.0   3216   884 pts/0    S+   18:57   0:00 grep --color=auto mysql
root@observium ~# kill -9 484
root@observium ~# service mysql start
root@observium ~# service mysql status
* mariadb.service - MariaDB 10.3.27 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-04-16 18:58:00 UTC; 4s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 19046 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
  Process: 19047 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 19049 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, sta
  Process: 19181 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 19183 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
 Main PID: 19150 (mysqld)
   Status: "Taking your SQL requests now..."
    Tasks: 31 (limit: 2355)
   Memory: 90.3M
   CGroup: /system.slice/mariadb.service
           `-19150 /usr/sbin/mysqld

Apr 16 18:58:00 observium mysqld[19150]: 2021-04-16 18:58:00 0 [Note] /usr/sbin/mysqld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 19150 ...
Apr 16 18:58:00 observium mysqld[19150]: 2021-04-16 18:58:00 0 [Warning] Could not increase number of max_open_files to more than 16384 (request: 32183)
Apr 16 18:58:00 observium systemd[1]: Started MariaDB 10.3.27 database server.
Apr 16 18:58:00 observium /etc/mysql/debian-start[19185]: Upgrading MySQL tables if necessary.
Apr 16 18:58:01 observium /etc/mysql/debian-start[19188]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 16 18:58:01 observium /etc/mysql/debian-start[19188]: Looking for 'mysql' as: /usr/bin/mysql
Apr 16 18:58:01 observium /etc/mysql/debian-start[19188]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 16 18:58:01 observium /etc/mysql/debian-start[19188]: This installation of MySQL is already upgraded to 10.3.27-MariaDB, use --force if you still need to run mysql_upgrade
Apr 16 18:58:01 observium /etc/mysql/debian-start[19196]: Checking for insecure root accounts.
Apr 16 18:58:01 observium /etc/mysql/debian-start[19200]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
lines 1-27/27 (END)

And here is the journalctl -u mariadb :

root@lg-info-observium ~# journalctl -u mariadb
-- Logs begin at Fri 2021-04-16 12:04:49 UTC, end at Fri 2021-04-16 19:00:45 UTC. --
Apr 16 18:54:14 lg-info-observium systemd[1]: mariadb.service: Found left-over process 484 (mysqld) in control group while starting unit. Ignoring.
Apr 16 18:54:14 lg-info-observium systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 16 18:54:14 lg-info-observium systemd[1]: Starting MariaDB 10.3.27 database server...
Apr 16 18:54:14 lg-info-observium systemd[1]: mariadb.service: Found left-over process 484 (mysqld) in control group while starting unit. Ignoring.
Apr 16 18:54:14 lg-info-observium systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 16 18:54:14 lg-info-observium mysqld[18922]: 2021-04-16 18:54:14 0 [Note] /usr/sbin/mysqld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 18922 ...
Apr 16 18:54:14 lg-info-observium mysqld[18922]: 2021-04-16 18:54:14 0 [Warning] Could not increase number of max_open_files to more than 16384 (request: 32183)
Apr 16 18:54:48 lg-info-observium systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Apr 16 18:57:46 lg-info-observium systemd[1]: mariadb.service: Failed with result 'exit-code'.
Apr 16 18:57:46 lg-info-observium systemd[1]: Failed to start MariaDB 10.3.27 database server.
Apr 16 18:58:00 lg-info-observium systemd[1]: Starting MariaDB 10.3.27 database server...
Apr 16 18:58:00 lg-info-observium mysqld[19150]: 2021-04-16 18:58:00 0 [Note] /usr/sbin/mysqld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 19150 ...
Apr 16 18:58:00 lg-info-observium mysqld[19150]: 2021-04-16 18:58:00 0 [Warning] Could not increase number of max_open_files to more than 16384 (request: 32183)
Apr 16 18:58:00 lg-info-observium systemd[1]: Started MariaDB 10.3.27 database server.
Apr 16 18:58:00 lg-info-observium /etc/mysql/debian-start[19185]: Upgrading MySQL tables if necessary.
Apr 16 18:58:01 lg-info-observium /etc/mysql/debian-start[19188]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 16 18:58:01 lg-info-observium /etc/mysql/debian-start[19188]: Looking for 'mysql' as: /usr/bin/mysql
Apr 16 18:58:01 lg-info-observium /etc/mysql/debian-start[19188]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 16 18:58:01 lg-info-observium /etc/mysql/debian-start[19188]: This installation of MySQL is already upgraded to 10.3.27-MariaDB, use --force if you still need to run mysql_upgrade
Apr 16 18:58:01 lg-info-observium /etc/mysql/debian-start[19196]: Checking for insecure root accounts.
Apr 16 18:58:01 lg-info-observium /etc/mysql/debian-start[19200]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables

 

 

Forum: 

Questions about Turnkey Observium appliance

$
0
0

Hello, Team

 

I am new to Turnkey products. I hope to use Observium appliance to monitor my network.

Here I have a few questions for Observium appliance:

1)I plan to deploy Observium appliance on VMware EXSi host.  How many CPU cores, memory and Hard drive are allocated by this Turnkey Observium appliance ?

2)Can I adjust the allocated resource for CPU Cores, Memory size and Hard drive ?

Regards,

Feng Li

 

Forum: 
Tags: 

observium poller

$
0
0

Cheers
It looks like the script to get equipment information passed from php to python (poller.php to poller-wrapper.py), but it starts with:
#! /usr/bin/env python
while the dvd iso has python3, so cron can't run it.

Sorry for the English, but my native language is Spanish although google does its best.

Forum: 
Viewing all 109 articles
Browse latest View live