This is the most useful command out there, now.
I was a sysadmin, and it is critical to know who is on your system. I may have to dig out the code and write this to a file. I want to provide the other admins, who do not have access to the Ubuntu box, an update every few minutes.
This is good mojo.
I had this cheesed up for a hint as to who might be on. get-users-last-login-date
This is much handier!
Thanks!
Thank you for the appreciative feedback 
For what Operating system do you need it? Maybe I can help to make it available for multiple OSes.
ernolf
This is utilized on Ubuntu 20.04 , but the monitor performs in a CLI, precluding use at the Nextcloud UI level. It would be helpful for a single-pass to show activity for active users. That output would be placed in a Note updated every few minutes so that the data is monitored at close enough intervals to show activity. Admins could then use that information to troubleshoot system issues, or just review system use.
Possibly beyond that, is similar to the System load monitor under the Administrative tab, exactly providing the currently provided activity status.
Even without that, there is finally a tool to indicate active users.
Thanks!
–Joe.
Attempting to change some system parameters, and hours later restoring NC functionality, and received the following that I’m not yet able to resolve:
/tmp/nc-who78672_oqoYn5EpLzUY: line 17: q0: command not found
Error: You must install at least one postgresql-client- package
I’ve got matching versions to postgresql-16 and postgresql-client-16.
Not sure where to go here. Is this system configuration related or an init that is required, as those packages had to be reinstalled?
Thanks,
–Joe.
Hi @corsairius,
The ebtb scripts and their modules cannot be changed that easily. They are the result of years of development. They are full of security layers that are designed to prevent the code from being changed. Tainted modules are immediately replaced with clean ones. After all, the scripts and modules are signed by me and as soon as you start tinkering with the script itself, things will at best no longer work. There’s a reason for everything. If you want to make changes, you should contact me via PM and explain exactly what you want to achieve.
I’ll then see if I can - and decide if I will help you.
Please don’t misunderstand me, but I cannot risk that scripts I have made publicly available could cause harm through changes.
The trust in my scripts that I have built up over the years is my most valuable asset. If that is destroyed, I can take everything offline.
h.t.h.
Much and good luck,
ernolf
I was not changing your utility’s system configuration. I was changing mine. There is no fault of your scripts here, and they are unchanged. I was curious as to my error in not seeing the postgresql-client call.
I was seeing if there was a remove and reinstall process, which may reread my system attributes on my Nextcloud instance.
thanks,
–Joe.
What I can tell from this error:
EDIT:
Thank you for that feedback, I could reconstruct and fix it.
“nc-who” speaks directly to the database and requires a command line client, either psql for postgreSQL or mysql for MariaDB. If no client is available or cannot be found, the operating system issues this error. At least it does not come from the script itself.
However, I would be interested to know if you can reconstruct the error without the script if you call psql.
ernolf
psql -p 5432 -h localhost -U nextcloud nextcloud
Password for user nextcloud:
psql (16.6 (Ubuntu 16.6-1.pgdg20.04+1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
Type "help" for help.
nextcloud=> SELECT * FROM pg_user;
usename | usesysid | usecreatedb | usesuper | userepl | usebypassrls | passwd | valuntil | useconfig
-----------+----------+-------------+----------+---------+--------------+----------+----------+-----------
postgres | 10 | t | t | t | t | ******** | |
nextcloud | 16388 | f | f | f | f | ******** | |
(2 rows)
nextcloud=>
But then it required a password to enter.
–Joe.
Of course you need the password when you connect “by feet” to the database comandline client. Because it does not have the magic of nc-who, nc-apps or nc-sql, handling the pasword stuf for you in the background.
ernolf
I haven’t seen anything new about this error in Brave searches, both AI and otherwise, except for the following issues with this particular error message.
Three items are indicated as resolution of the issue.
So far uninstalling and reinstalling Postgresql-16, and harrowingly losing Nextcloud database a couple times, that hasn’t changed receipt of the error code. I’ve also uninstalled postgresql-common, and postgresql-client-common, kinda repeating the above heart attack stuff… 
But I know more about recovery and interactions with NC now.
I’m hoping that a re-init of nc-who would suffice?
Thanks!
–Joe.
Hi @corsairius,
I have researched the problem you described to the bottom of it. At first I couldn’t explain it to myself because it worked perfectly for me in different environments, but in the end I was able to reconstruct it and implement a solution.
Please try again and give me feedback on whether it has now been solved for you.
ernolf
It works again. Thanks!
–Joe.
Sent a coffee
Hello, https://global-social.net seem not to work I couldn’t download nc-who.
Best regards
@ernolf now it seems to work for download.
It is possible to see client IP in nc-who ?
Of which device of the user?
It is technically possible but I didn’t integrate that on purpose.
You can see the remote addresses from the → audit log ← file.
Here I described how to filter that:
h.t.h.
Much and good luck,
ernolf