Home
NFS in fstab fails to mount at boot
Turns out that in Debian 9, NFS entries in the fstab don't come up at boot time. At boot, systemd autodetects that the type is NFS and _should_ wait for networking, but it doesn't and no amount of _netdev or other things seem to work. Turns out to be the way the interface is presented from the network config file. Change the interface: from allow-hotplug ens192 to auto ens192 The Clue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792030 No Help: https://unix.stackexchange.com/questions/349264/fstab-mount-wait-for-network |
mount error(112): Host is down
If you get this in linux when mounting a windows 10 share, it's because you need to specify the SMB version |
adduser: The --group, --ingroup, and --gid options are mutually exclusive.
You may go to create a service account with a known UID and GID like so: You might be tempted to just omit the group. However, that command
attempts to create a group if that matches the user id, and you may find
you have more groups than users.sudo adduser --system --no-create-home --disabled-login --uid 112 --group --gid 117 some-serviceHowever, that command can't be done on one line. adduser: The --group, --ingroup, and --gid options are mutually exclusive.adduser: The GID 112 is already in use.So make it a two-liner sudo addgroup --gid 117 some-servicesudo adduser --system --no-create-home --disabled-login --uid 112 --gid 117 some-service |
Dynamic Address Static DNS Order
By default, you can add name servers to your /etc/networking/interfaces file, but you'll still get the DHCP supplied ones first. To change that, you must supercede that in the /etc/resolv.conf options. |
Unknown USB bridge
When checking a disk with smartmontools, you may get this
Check the page below and add the -d option.
If that fails, you may need to switch from the newer 'uac' usb driver back to the old one |
HPDBA0235I The server lost the client's authentication
When configuring ISIM to talk to ISAM, you have to deploy and configure the Java Run Time. If you get the above exception when issuing the
com.tivoli.pd.jcfg.SvrSslCfg it's likely because your local copy of PD.jar is out of date. The answer is to download the most recent pdjrte from the ISAM appliance and redeploy. https://www-304.ibm.com/connections/blogs/havan/entry/debugging_an_isam_java_runtime_ssl_handhake_in_websphere?lang=en_us |
NXLOG Couldn't read next event
If you see this error message from nxlog:
Congrats - you've hit a bug.
The work-around is to limit your log event subscriptions on the input side by using a query. Example:
|
Kibana rounding to 16 significant digits
Turns out, if you have a value of type integer, that's just the limit. While elasticsearch shows you this:
Kibana shows you this Looking at the JSON will give you the clue - it's being treated as an integer and not a string. "_source": { "requester_name": "8163783564660983218", "request_num": 8163783618037079000, "started": "2016-04-07 15:16:16:139 GMT", "completed": "2016-04-07 15:16:16:282 GMT", Mutate it to string in logstash to get your precision back. https://github.com/elastic/kibana/issues/4356 |
Reset Chrome Magnet Link Handling
Picked the wrong thing when chrome first asked you, or chrome is just opening a new window on ubuntu? Have it ask you again by deleting the file that tells it what to do with external protocols |
1-10 of 46