Posted by jpluimers on 2016/09/14
The ESXi console top to show processes is not available *, the alternative is esxtop. But that can show garbage because the ESXi console has a very limited support of terminals **.
For instance, when connecting from a Mac OS X terminal through ssh, this is my terminal:
# echo $TERM
xterm-256color
The solution:
TERM=xterm esxtop
–jeroen
via: VMware KB: Output of esxtop defaults to non-interactive CSV with unknown TermInfo.
Posted in *nix, *nix-tools, bash, bash, Development, ESXi5, ESXi5.1, ESXi5.5, ESXi6, Power User, Scripting, Virtualization, VMware, VMware ESXi | 2 Comments »
Posted by jpluimers on 2016/09/13
These two vim-cmd scripts come in very handy:
| #!/bin/sh | |
| VMS=`vim-cmd vmsvc/getallvms | grep -v Vmid | awk '{print $1}'` | |
| for VM in $VMS ; do | |
| # echo "Probing VM with id: $VM." | |
| PWR=`vim-cmd vmsvc/power.getstate $VM | grep -v "Retrieved runtime info"` | |
| name=`vim-cmd vmsvc/get.config $VM | grep -i "name =" | awk '{print $3}' | head -1 | awk -F'"' '{print $2}'` | |
| echo "VM with id $VM has power state $PWR (name = $name)." | |
| done |
| #!/bin/sh | |
| # https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/ | |
| RUNNING=0 | |
| vmids=`vim-cmd vmsvc/getallvms | sed -n -E -e "s/^([[:digit:]]+)\s+((\S.+\S)?)\s+(\[\S+\])\s+(.+\.vmx)\s+(\S+)\s+(vmx-[[:digit:]]+)\s*?((\S.+)?)$/\1/p"` | |
| for vmid in ${vmids} ; do | |
| # echo "Probing VM with id: $vmid." | |
| powerState=`vim-cmd vmsvc/power.getstate ${vmid} | sed '1d'` | |
| name=`vim-cmd vmsvc/get.config ${vmid} | sed -n -E -e '/\(vim.vm.ConfigInfo\) \{/,/files = \(vim.vm.FileInfo\) \{/ s/^ +name = "(.*)",.*?/\1/p'` | |
| vmPathName=`vim-cmd vmsvc/get.config ${vmid} | sed -n -E -e '/files = \(vim.vm.FileInfo\) \{/,/tools = \(vim.vm.ToolsConfigInfo\) \{/ s/^ +vmPathName = "(.*)",.*?/\1/p'` | |
| # echo "VM with id ${vmid} has power state ${powerState} (name = ${name}; vmPathName = ${vmPathName})." | |
| if [ "${powerState}" == "Powered on" ] ; then | |
| RUNNING=1 | |
| echo "Powered on VM with id ${vmid} and name: $name" | |
| echo "Suspending VM with id ${vmid} and name: $name" | |
| vim-cmd vmsvc/power.suspend ${vmid} > /dev/null & | |
| fi | |
| done | |
| while true ; do | |
| if [ $RUNNING -eq 0 ] ; then | |
| echo "Gone…" | |
| break | |
| fi | |
| RUNNING=0 | |
| for vmid in ${vmids} ; do | |
| # echo "Probing VM with id: $vmid." | |
| powerState=`vim-cmd vmsvc/power.getstate ${vmid} | sed '1d'` | |
| name=`vim-cmd vmsvc/get.config ${vmid} | sed -n -E -e '/\(vim.vm.ConfigInfo\) \{/,/files = \(vim.vm.FileInfo\) \{/ s/^ +name = "(.*)",.*?/\1/p'` | |
| vmPathName=`vim-cmd vmsvc/get.config ${vmid} | sed -n -E -e '/files = \(vim.vm.FileInfo\) \{/,/tools = \(vim.vm.ToolsConfigInfo\) \{/ s/^ +vmPathName = "(.*)",.*?/\1/p'` | |
| # echo "VM with id ${vmid} has power state ${powerState} (name = ${name}; vmPathName = ${vmPathName})." | |
| if [ "${powerState}" == "Powered on" ] ; then | |
| RUNNING=1 | |
| echo "Waiting for id ${vmid} and name: $name…" | |
| fi | |
| done | |
| sleep 1 | |
| done | |
| exit 0 |
| #!/bin/sh | |
| SUSPENDED=0 | |
| VMS=`vim-cmd vmsvc/getallvms | grep -v Vmid | awk '{print $1}'` | |
| VMstateToProcess="Suspended" | |
| for VM in $VMS ; do | |
| # echo "Probing VM with id: $VM." | |
| PWR=`vim-cmd vmsvc/power.getstate $VM | grep -v "Retrieved runtime info"` | |
| name=`vim-cmd vmsvc/get.config $VM | grep -i "name =" | awk '{print $3}' | head -1 | awk -F'"' '{print $2}'` | |
| echo "VM with id $VM has power state $PWR (name = $name)." | |
| if [ "$PWR" == "$VMstateToProcess" ] ; then | |
| SUSPENDED=1 | |
| echo "Suspended VM with id $VM and name: $name" | |
| echo "Resuming VM with id $VM and name: $name" | |
| # you'd think power.suspendResume is the inverse of power.suspend, but actually power.on is: | |
| vim-cmd vmsvc/power.on $VM > /dev/null & | |
| fi | |
| done | |
| while true ; do | |
| if [ $SUSPENDED -eq 0 ] ; then | |
| echo "Gone…" | |
| break | |
| fi | |
| SUSPENDED=0 | |
| for VM in $VMS ; do | |
| PWR=`vim-cmd vmsvc/power.getstate $VM | grep -v "Retrieved runtime info"` | |
| if [ "$PWR" == "$VMstateToProcess" ] ; then | |
| name=`vim-cmd vmsvc/get.config $VM | grep -i "name =" | awk '{print $3}' | head -1 | awk -F'"' '{print $2}'` | |
| echo "Waiting for id $VM and name: $name…" | |
| SUSPENDED=1 | |
| fi | |
| done | |
| sleep 1 | |
| done |
–jeroen
Posted in bash, Development, ESXi4, ESXi5, ESXi5.1, ESXi5.5, ESXi6, Power User, Scripting, Software Development, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2016/09/12
Be careful with setting the timeout of sendmail to zero when trying to flush the mail queue:
sendmail -OTimeout.hoststatus=0m -q -v
Reason: a lot of target systems do rate-limiting if you retry too much in too short time, for instance gmail does that:
421-4.7.0 [###.###.###.### 15] Our system has detected an unusual rate of
421-4.7.0 unsolicited mail originating from your IP address. To protect our
421-4.7.0 users from spam, mail sent from your IP address has been temporarily
421-4.7.0 rate limited. Please visit
421-4.7.0 https://support.google.com/mail/answer/81126 to review our Bulk Email
421 4.7.0 Senders Guidelines. w1si28749381wju.16 - gsmtp
–jeroen
via Flush deferred messages in sendmail queue :: Stephan Paukner :: syslog.
Posted in *nix, *nix-tools, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2016/09/10
It was fun while it lasted:
No SponsorsPage2rss.com currently does not have any sponsors for you.
Source: Page2rss.com
Anyone who has good alternatives for it?
–jeroen
PS: I’ll give this a try: PageMon.Net: The Page Monitor [pre-alpha]
Posted in Power User, RSS, SocialMedia | Leave a Comment »
Posted by jpluimers on 2016/09/09
Using Reaper To Normalize Your Tracks To The Same LUFS. It’s a SNAP! – Mack Caster
Source: Hello again Dawn. This is for you. :-) Using Reaper To Normalize Your Tracks To…
If you want to know more about LUFS (which is a synonym for LKFS), then read these:
–jeroen
Posted in Audio, LifeHacker, Normalisation of audio, Power User, Reaper | Leave a Comment »
Posted by jpluimers on 2016/09/09
On some systems, after upgrading OpenSuSE Tumbleweed to 20160905 ntp stops working.
Pending the verification of snapshot 20160908 (not finished yet), if if you have updated to 20160905 or 20160907,, the bogus ntp version is, so you have to downgrade:
zypper in --oldpackage http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/ntp-4.2.8p8-1.3.x86_64.rpm systemctl restart ntpd.service
Or wait a few hours and install snapshot 20160908.
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2016/09/07
I figured this out, it turned out to be a DNS resolution issue. For some reason leaving ‘search localdomain’ in resolv.conf generates some slowness. I’m not sure if it’s because 127.0.0.1 isn’t mapped to ‘localhost.localdomain’ in /etc/hosts by default, or whatever, but taking it out fixes the performance issue.
Source: TUMBLEWEED Poor performance in VMware Fusion
–jeroen
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2016/09/07
This succeeded: https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumbleweed&build=20160901&groupid=1 installing the image from http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso.mirrorlist (for which the md5 and sha signatures match).
But I got this cd:/content: Invalid signature. Installation aborted. message:
After a few statements [WayBack] in the install shell:
mkdir /mnt/cd
mount /dev/cdrom /mnt/cd
cd /mnt/cd
gpg --import content.key
gpt --verify content.asc
Indeed the cd:/content didn’t verify as content.key wasn’t a trusted signature:
–jeroen
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2016/09/07
Oddest OpenSuSE Tumbleweed installation screen colours ever…
Source: Screenshot 2016-09-07 15.51.08.png
Posted in Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2016/09/06
One thing I’ve not figured out yet is this: How does enabling btrfs quotas impact the system? – Unix & Linux Stack Exchange
My gut feeling says it’s not much. But if someone knows: please chime in.
Anyway: btrfs quota support helps you to see how big snapshots (and other subvolumes) are.
Enabling and disabling is easy (the slash is the path from where to enable quota):
btrfs quota enable /
btrfs quota disable /
The bad thing is that there is no command that gives just the quota status. You have to revert to btrfs qgroup show /
This will show you quota groups when quota are enabled:
qgroupid rfer excl -------- ---- ---- 0/5 16.00KiB 16.00KiB
or errors when quota are disabled either of these two errors:
# btrfs qgroup show / ERROR: can't perform the search - No such file or directory ERROR: can't list qgroups: No such file or directory # btrfs qgroup show / ERROR: can't list qgroups: quotas not enabled
You might also want to check the syslogs as there was a [PATCH 1/2] btrfs: syslog when quota is enabled.
The btrfs qgroup output is the base for agronick/btrfs-size: A script that will print out a list of BTRFS subvolumes along with their size in megabytes and their name.
It actually shows it in human readable form (kilo/mega/giga/… bytes) and is documented at Get the size of your BTRFS Snapshots | PoisonPacket. It gives me a nice overview that corresponds to the snapper list output (see below).
The script has two drawbacks:
./btrfs-size/btrfs-size.sh: line 55: can't + 0: syntax error: invalid arithmetic operator (error token is "'t + 0")
btrfs quota enable / to actually deliver the quota for all the qgroupid values snapper uses. Until that time, the columns ID/Total/Exclusive Data are empty.
# btrfs qgroup show / > /dev/null
WARNING: Qgroup data inconsistent, rescan recommended
In that case, run btrfs quota rescan / and wait for it to complete by running this command until the warning is gone:
# btrfs qgroup show / > /dev/null
WARNING: Rescan is running, qgroup data may be incorrect
If the warning reverts to WARNING: Qgroup data inconsistent, rescan recommended then you might see the effects from this bug and should not worry about it: Bug 933428 – btrfs qgroup – allways shows WARNING: Qgroup data inconsistent.
For more btrfs quota background information, see: UseCases – btrfs Wiki.
–jeroen
Posted in *nix, *nix-tools, bash, Development, Linux, openSuSE, Power User, Scripting, Software Development, SuSE Linux, Tumbleweed | 1 Comment »
The Wiert Corner - irregular stream of stuff 