Forums

Fri
Fri
Offline
Resolved
0 votes
1. Does ClearOS have a feature that when ever a end user goes to facebook.com ClearOS logs the Computer name and date/time? I don't want to block the facebook, I just want to see who is using facebook during work hour.
2. Filter and Proxy Report and another reports loading forever. Is there a fix for this?
Tuesday, March 17 2020, 08:15 AM
Share this post:
Responses (20)
  • Accepted Answer

    Tuesday, March 17 2020, 08:51 AM - #Permalink
    Resolved
    1 votes
    The only obvious way is to use the Proxy in non-transparent and authenticated mode, but this set up is obtrusive in that you have to reconfigure every PC to use the proxy or use Web Proxy Auto-discovery (WPAD). The proxy is quite resource intensive and, depending on the speed of your line, is probably best run cachless (check its documentation). Netify may be able to do what you want but I don't know it well.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, March 18 2020, 10:12 AM - #Permalink
    Resolved
    1 votes
    Can you give a screendump of the reports issue?
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, March 18 2020, 01:43 PM - #Permalink
    Resolved
    1 votes
    It depends on what you are doing. I run VM's with 1.5GB, but ClamAV will struggle as may the Proxy (if you use it). As far as I can see, you often get a high swap usage on boot up.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 19 2020, 10:19 AM - #Permalink
    Resolved
    1 votes
    ClamAV is also the File Scanner and Mail Antivirus. There is no guarantee that upgrading to 8GB will get rid of the warning. Note it is only a 1-off warning. Have a look at your swap file usage with "free" or "top".

    Having said that, it is fine to have swap file usage high as long as you have reasonable available memory. ClearOS may have parked stuff in the swap file that it is hardly using and there is no harm it being there. What you don't want is to have ClearOS constantly swapping stuff in and out, but I am not sure how you monitor that, but Google is your friend.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 19 2020, 09:15 PM - #Permalink
    Resolved
    1 votes
    You could try resetting the reports database. You can log on to the system database and drop the reports database with something like:
    /usr/clearos/sandbox/usr/bin/mysql -u root -p`cut -f3 -d" " /var/clearos/system_database/root` -e 'drop database reports;'
    Then re-initialise the database with:
    /usr/clearos/apps/reports_database/deploy/initialize-database
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 20 2020, 08:58 AM - #Permalink
    Resolved
    1 votes
    No, the command is for the sandboxed system-mariadb server. Is it running?
    systemctl status system-mariadb
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 20 2020, 02:41 PM - #Permalink
    Resolved
    1 votes
    So try and start it (change status to start). If it fails, check the log (/var/log/system-mariadb/mariadb.log) and, perhaps, the messages log for errors. Also "journalctl -xe".
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, March 21 2020, 10:21 AM - #Permalink
    Resolved
    1 votes
    So "journalclt -xe" reveals nothing. Does "systemctl status system-mariadb -l" show anything? Also what do you get from:
    mysql -V
    ls -l /var/log/system-mariadb/
    Did /var/log/messages show anything?

    [edit]
    You could try expanding your screen before running "journalctl -xe" as the output is being truncated.
    [/edit]
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, March 22 2020, 09:27 AM - #Permalink
    Resolved
    1 votes
    "journalctl -xe" needs to be run straight after system-mmariadb fails to start. The other two commands are not showing anything obvious. You may need to remove system-mariadb and the contents of /var/clearos/system_database/* and reinstalling it. I've done it once and can't remember how.

    What do you get from:
    yum remove system-mariadb --assumeno
    Please put the results between code tags (the piece of paper icon with a <> on it).
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Monday, March 23 2020, 09:35 AM - #Permalink
    Resolved
    1 votes
    I **think** you can go ahead with that:
    yum remove system-mariadb
    Then remove or rename /var/lib/system-mysql. Then try reinstalling:
    yum install app-system-database-core
    If that works and gets system-mariadb up and running, you can then reinstall your reports.

    As a warning, if this goes wrong I may not be able to fix it.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Wednesday, March 18 2020, 01:41 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    The only obvious way is to use the Proxy in non-transparent and authenticated mode, but this set up is obtrusive in that you have to reconfigure every PC to use the proxy or use Web Proxy Auto-discovery (WPAD). The proxy is quite resource intensive and, depending on the speed of your line, is probably best run cachless (check its documentation). Netify may be able to do what you want but I don't know it well.


    Maybe I just install a third party software all in the computer.

    I have one more problem in the reports panel. They all just Loading forever it wont show any grap or reports.
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Wednesday, March 18 2020, 10:27 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Can you give a screendump of the reports issue?


    High swap memory usage ($swap_usage%)

    I have 3GB RAM. Do I need more RAM?
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Thursday, March 19 2020, 04:16 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    It depends on what you are doing. I run VM's with 1.5GB, but ClamAV will struggle as may the Proxy (if you use it). As far as I can see, you often get a high swap usage on boot up.


    ClamAV is the Gateway Antiphising and Antivus right?

    If I upgrade my 3GB memory to 8GB this warning event "High swap memory usage ($swap_usage%)" will be fix?
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Thursday, March 19 2020, 01:13 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    ClamAV is also the File Scanner and Mail Antivirus. There is no guarantee that upgrading to 8GB will get rid of the warning. Note it is only a 1-off warning. Have a look at your swap file usage with "free" or "top".

    Having said that, it is fine to have swap file usage high as long as you have reasonable available memory. ClearOS may have parked stuff in the swap file that it is hardly using and there is no harm it being there. What you don't want is to have ClearOS constantly swapping stuff in and out, but I am not sure how you monitor that, but Google is your friend.


    Network Report, Resource report not loading up.
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Friday, March 20 2020, 01:48 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    You could try resetting the reports database. You can log on to the system database and drop the reports database with something like:
    /usr/clearos/sandbox/usr/bin/mysql -u root -p`cut -f3 -d" " /var/clearos/system_database/root` -e 'drop database reports;'
    Then re-initialise the database with:
    /usr/clearos/apps/reports_database/deploy/initialize-database


    There is an error.

    Can't connect to local MySQL server through socket '/var/lib/system-mysql/mysql.sock' (111)

    this command is for the MariaDB Database Server?
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Friday, March 20 2020, 12:27 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    No, the command is for the sandboxed system-mariadb server. Is it running?
    systemctl status system-mariadb


    ● system-mariadb.service - System MariaDB database server
    Loaded: loaded (/usr/lib/systemd/system/system-mariadb.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Sat 2020-03-07 17:56:42 PST; 1 weeks 6 days ago
    Process: 1560 ExecStartPost=/usr/clearos/sandbox/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
    Process: 1559 ExecStart=/usr/clearos/sandbox/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
    Process: 1353 ExecStartPre=/usr/clearos/sandbox/usr/libexec/mariadb-prepare-db-dir (code=exited, status=0/SUCCESS)
    Main PID: 1559 (code=exited, status=0/SUCCESS)

    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Saturday, March 21 2020, 06:37 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    So try and start it (change status to start). If it fails, check the log (/var/log/system-mariadb/mariadb.log) and, perhaps, the messages log for errors. Also "journalctl -xe".


    It fails to start.

    /var/log/system-mariadb/mariadb.log

    -bash: /var/log/system-mariadb/mariadb.log: Permission denied.

    journalctl -xe
    Mar 21 14:32:41 frontken.com.ph kernel: ata2.00: cmd 60/08:40:78:ee:8c/00:00:00:
    res 41/40:08:78:ee:8c/00:00:00:
    Mar 21 14:32:41 frontken.com.ph kernel: ata2.00: status: { DRDY ERR }
    Mar 21 14:32:41 frontken.com.ph kernel: ata2.00: error: { UNC }
    Mar 21 14:32:41 frontken.com.ph kernel: ata2.00: configured for UDMA/133
    Mar 21 14:32:41 frontken.com.ph kernel: sd 2:0:0:0: [sdb] tag#8 FAILED Result: h
    Mar 21 14:32:41 frontken.com.ph kernel: sd 2:0:0:0: [sdb] tag#8 Sense Key : Medi
    Mar 21 14:32:41 frontken.com.ph kernel: sd 2:0:0:0: [sdb] tag#8 Add. Sense: Unre
    Mar 21 14:32:41 frontken.com.ph kernel: sd 2:0:0:0: [sdb] tag#8 CDB: Read(10) 28
    Mar 21 14:32:41 frontken.com.ph kernel: blk_update_request: I/O error, dev sdb,
    Mar 21 14:32:41 frontken.com.ph kernel: ata2: EH complete
    Mar 21 14:32:46 frontken.com.ph systemd[1]: system-mariadb.service: control proc
    Mar 21 14:32:46 frontken.com.ph systemd[1]: Failed to start System MariaDB datab
    -- Subject: Unit system-mariadb.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit system-mariadb.service has failed.
    --
    -- The result is failed.
    Mar 21 14:32:46 frontken.com.ph systemd[1]: Unit system-mariadb.service entered
    Mar 21 14:32:46 frontken.com.ph systemd[1]: system-mariadb.service failed.
    Mar 21 14:32:46 frontken.com.ph polkitd[791]: Unregistered Authentication Agent
    lines 996-1018/1018 (END)
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Sunday, March 22 2020, 09:09 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    So "journalclt -xe" reveals nothing. Does "systemctl status system-mariadb -l" show anything? Also what do you get from:
    mysql -V
    ls -l /var/log/system-mariadb/
    Did /var/log/messages show anything?

    [edit]
    You could try expanding your screen before running "journalctl -xe" as the output is being truncated.
    [/edit]


    [root@frontken ~]# journalctl -xe
    Mar 22 17:01:01 frontken.com.ph sudo[29696]: pam_unix(sudo:session): session ope
    Mar 22 17:01:01 frontken.com.ph sudo[29696]: pam_unix(sudo:session): session clo
    Mar 22 17:01:01 frontken.com.ph sudo[29699]: pam_unix(sudo:session): session ope
    Mar 22 17:01:01 frontken.com.ph sudo[29699]: pam_unix(sudo:session): session clo
    Mar 22 17:01:01 frontken.com.ph sudo[29702]: pam_unix(sudo:session): session ope
    Mar 22 17:01:01 frontken.com.ph sudo[29702]: pam_unix(sudo:session): session clo
    Mar 22 17:01:01 frontken.com.ph sudo[29705]: pam_unix(sudo:session): session ope
    Mar 22 17:01:01 frontken.com.ph sudo[29705]: pam_unix(sudo:session): session clo
    Mar 22 17:01:01 frontken.com.ph sudo[29708]: pam_unix(sudo:session): session ope
    Mar 22 17:01:01 frontken.com.ph sudo[29708]: pam_unix(sudo:session): session clo
    Mar 22 17:01:01 frontken.com.ph sudo[29711]: pam_unix(sudo:session): session ope
    Mar 22 17:01:01 frontken.com.ph sudo[29711]: pam_unix(sudo:session): session clo
    Mar 22 17:01:21 frontken.com.ph sshd[29725]: Accepted password for root from 10.
    Mar 22 17:01:21 frontken.com.ph systemd-logind[786]: New session 21787 of user r
    -- Subject: A new session 21787 has been created for user root
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
    --
    -- A new session with the ID 21787 has been created for the user root.
    --
    -- The leading process of the session is 29725.
    Mar 22 17:01:21 frontken.com.ph sshd[29725]: pam_unix(sshd:session): session ope
    lines 987-1009/1009 (END)
    Mar 22 17:01:01 frontken.com.ph sudo[29696]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Mar 22 17:01:01 frontken.com.ph sudo[29696]: pam_unix(sudo:session): session closed for user root
    Mar 22 17:01:01 frontken.com.ph sudo[29699]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Mar 22 17:01:01 frontken.com.ph sudo[29699]: pam_unix(sudo:session): session closed for user root
    Mar 22 17:01:01 frontken.com.ph sudo[29702]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Mar 22 17:01:01 frontken.com.ph sudo[29702]: pam_unix(sudo:session): session closed for user root
    Mar 22 17:01:01 frontken.com.ph sudo[29705]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Mar 22 17:01:01 frontken.com.ph sudo[29705]: pam_unix(sudo:session): session closed for user root
    Mar 22 17:01:01 frontken.com.ph sudo[29708]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Mar 22 17:01:01 frontken.com.ph sudo[29708]: pam_unix(sudo:session): session closed for user root
    Mar 22 17:01:01 frontken.com.ph sudo[29711]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Mar 22 17:01:01 frontken.com.ph sudo[29711]: pam_unix(sudo:session): session closed for user root
    Mar 22 17:01:21 frontken.com.ph sshd[29725]: Accepted password for root from 10.210.203.245 port 54394 ssh2
    Mar 22 17:01:21 frontken.com.ph systemd-logind[786]: New session 21787 of user root.
    -- Subject: A new session 21787 has been created for user root
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
    --
    -- A new session with the ID 21787 has been created for the user root.
    --
    -- The leading process of the session is 29725.
    Mar 22 17:01:21 frontken.com.ph sshd[29725]: pam_unix(sshd:session): session opened for user root by (uid=0)


    and

    [root@frontken ~]# mysql -V
    mysql Ver 15.1 Distrib 5.5.64-MariaDB, for Linux (x86_64) using readline 5.1
    [root@frontken ~]# ls -l /var/log/system-mariadb/
    total 12
    -rw-r----- 1 system-mysql system-mysql 0 Mar 22 03:46 mariadb.log
    -rw-r----- 1 system-mysql system-mysql 776 Mar 6 19:04 mariadb.log-20200307.gz
    -rw-r----- 1 system-mysql system-mysql 905 Mar 7 17:56 mariadb.log-20200308.gz
    -rw-r----- 1 system-mysql system-mysql 943 Mar 21 14:32 mariadb.log-20200322.gz
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Sunday, March 22 2020, 11:07 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    "journalctl -xe" needs to be run straight after system-mmariadb fails to start. The other two commands are not showing anything obvious. You may need to remove system-mariadb and the contents of /var/clearos/system_database/* and reinstalling it. I've done it once and can't remember how.

    What do you get from:
    yum remove system-mariadb --assumeno
    Please put the results between code tags (the piece of paper icon with a <> on it).


    [root@frontken ~]# yum remove system-mariadb --assumeno
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Resolving Dependencies
    --> Running transaction check
    ---> Package system-mariadb.x86_64 1:5.5.60-1.v7.1 will be erased
    --> Processing Dependency: system-mariadb(x86-64) = 1:5.5.60-1.v7.1 for package: 1:system-mariadb-server-5.5.60-1.v7.1.x86_64
    --> Running transaction check
    ---> Package system-mariadb-server.x86_64 1:5.5.60-1.v7.1 will be erased
    --> Processing Dependency: system-mariadb-server >= 1:5.5.52-2 for package: 1:ap p-system-database-core-2.3.4-1.v7.noarch
    --> Running transaction check
    ---> Package app-system-database-core.noarch 1:2.3.4-1.v7 will be erased
    --> Processing Dependency: app-system-database-core >= 1:1.2.4 for package: 1:ap p-reports-database-core-2.5.0-1.v7.noarch
    --> Running transaction check
    ---> Package app-reports-database-core.noarch 1:2.5.0-1.v7 will be erased
    --> Processing Dependency: app-reports-database-core >= 1:1.4.8 for package: 1:a pp-proxy-report-core-2.5.0-1.v7.noarch
    --> Processing Dependency: app-reports-database-core >= 1:2.3.0 for package: 1:a pp-resource-report-core-2.5.0-1.v7.noarch
    --> Processing Dependency: app-reports-database-core >= 1:2.3.0 for package: 1:a pp-network-report-core-2.5.0-1.v7.noarch
    --> Running transaction check
    ---> Package app-network-report-core.noarch 1:2.5.0-1.v7 will be erased
    --> Processing Dependency: app-network-report-core = 1:2.5.0-1.v7 for package: 1 :app-network-report-2.5.0-1.v7.noarch
    ---> Package app-proxy-report-core.noarch 1:2.5.0-1.v7 will be erased
    --> Processing Dependency: app-proxy-report-core = 1:2.5.0-1.v7 for package: 1:a pp-proxy-report-2.5.0-1.v7.noarch
    ---> Package app-resource-report-core.noarch 1:2.5.0-1.v7 will be erased
    --> Processing Dependency: app-resource-report-core = 1:2.5.0-1.v7 for package: 1:app-resource-report-2.5.0-1.v7.noarch
    --> Running transaction check
    ---> Package app-network-report.noarch 1:2.5.0-1.v7 will be erased
    ---> Package app-proxy-report.noarch 1:2.5.0-1.v7 will be erased
    ---> Package app-resource-report.noarch 1:2.5.0-1.v7 will be erased
    --> Finished Dependency Resolution

    Dependencies Resolved

    ================================================================================
    Package Arch Version Repository Size
    ================================================================================
    Removing:
    system-mariadb x86_64 1:5.5.60-1.v7.1 @clearos-updates 49 M
    Removing for dependencies:
    app-network-report noarch 1:2.5.0-1.v7 @clearos-updates 9.4 k
    app-network-report-core noarch 1:2.5.0-1.v7 @clearos-updates 12 k
    app-proxy-report noarch 1:2.5.0-1.v7 @clearos-updates 28 k
    app-proxy-report-core noarch 1:2.5.0-1.v7 @clearos-updates 67 k
    app-reports-database-core noarch 1:2.5.0-1.v7 @clearos-updates 28 k
    app-resource-report noarch 1:2.5.0-1.v7 @clearos-updates 17 k
    app-resource-report-core noarch 1:2.5.0-1.v7 @clearos-updates 18 k
    app-system-database-core noarch 1:2.3.4-1.v7 @clearos-verified 20 k
    system-mariadb-server x86_64 1:5.5.60-1.v7.1 @clearos-updates 59 M

    Transaction Summary
    ================================================================================
    Remove 1 Package (+9 Dependent packages)

    Installed size: 107 M
    Exiting on user command
    Your transaction was saved, rerun it with:
    yum load-transaction /tmp/yum_save_tx.2020-03-23.07-04.gmOGvt.yumtx
    The reply is currently minimized Show
  • Accepted Answer

    Fri
    Fri
    Offline
    Monday, March 23 2020, 10:07 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    I **think** you can go ahead with that:
    yum remove system-mariadb
    Then remove or rename /var/lib/system-mysql. Then try reinstalling:
    yum install app-system-database-core
    If that works and gets system-mariadb up and running, you can then reinstall your reports.

    As a warning, if this goes wrong I may not be able to fix it.


    I will try this in the near future as for now. I will use another software like AcTivtrak it has the feature that I need.

    Thanks for your help Nick.
    The reply is currently minimized Show
Your Reply