Pocket button does not save any urls

Saving urls using the Pocket Pocket service service has failed within Firefox.
I am running the Windows 7 version of firefox with a couple of useful extensions.
The Pocket account has already been set up and authentication to the Pocket service works fine.
To make it work again, all the addons and extensions have been disabled for troubleshooting. No success.
I had to reinstall Firefox and delete my profile as indicated below :
How to successfully uninstall Firefox under Windows 7

Once completed and after adding the Pocket button into the firefox toobar, Saving urls with the Pocket service works fine again.

More information here :
Saving to Pocket and Accessing your List in Firefox

vSphere vCenter : 503 service unavailable

Having either of these errors can lead to some services not started on the vCenter server.



503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:00000000011D7F00] _serverNamespace = / _isRedirect = false _pipeName =\\.\pipe\vmware-vpxd-webserver-pipe)

503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:00000000012B0BA0] _serverNamespace = /vsphere-client _isRedirect = false _port = 9090)

If your vCenter is running on a Windows box, checking the status of its services can provide some first-hand information :

cd C:\Program Files\VMware\vCenter Server\bin

./service-control --status

To stop all the services :
./service-control --stop --all

To start all the services :
./service-control --start --all

VMWare KB 2109881

Check which installed packages on your system are not supported

To have a quick summary of which installed packages on your system are not supported, install the debian-security-support :

[root@localhost:~#] apt-get install debian-security-support

A check for new unsupported packages is run everytime new packages are installed.

check-support-status utility can be run manually as well to get a list of all the unsupported packages installed on your system.

bash : /usr/share/bash-completion/bash_completion : line 226 : syntax error near unexpected token ‘}’

While using bash auto-completion feature, you may have the following error :
“bash : /usr/share/bash-completion/bash_completion : line 226 : syntax error near unexpected token ‘}'”

Make sure not to have any bash keywords like ‘do’, ‘done’ as an alias in your own bashrc file.
Rename your alias and reload your updated bashrc file. Auto-completion works fine now in your bash shell.

http://comments.gmane.org/gmane.comp.shells.bash.completion.devel/5145

http://stackoverflow.com/questions/22969050/bash-syntax-error-near-unexpected-token-done-with-alias-named-do

XDG: configuration directory ‘/home/fool/.config/newsbeuter’ not accessible, using ‘/home/fool/.newsbeuter’ instead.

On Debian Jessie, I get this error while launching newsbeuter :

“XDG: configuration directory ‘/home/fool/.config/newsbeuter’ not accessible, using ‘/home/fool/.newsbeuter’ instead.”

XDG stands for X Desktop Group and now known as the freedesktop.org project.
More details about XDG

To fix it, here is the workaround :

fool@localhost:~$ cd /home/fool/.config/
fool@localhost:~$ ln -s ~/.newsbeuter/ newsbeuter

Once done, you might have another similar error :

“XDG: data directory ‘/home/fool/.local/share/newsbeuter’ not accessible, using ‘/home/fool/.newsbeuter’ instead.”

To fix it, here is the workaround :

fool@localhost:~$ cd /home/fool/.local/share/
fool@localhost:~$ ln -s ~/.newsbeuter/ newsbeuter

Hope this helps !

New DNS entries added while joining a Windows domain

Beware of rejoining a Linux server to a Windows domain.
After restarting winbind service and rejoining a server running RHEL 6.6 within a Windows domain, the monitoring of this server and its services started to be a real mess, sending false alerts.
After investigation, new DNS entries were added. The DNS name was the same pointing to different IP addresses, the ones set up on the server.
By default, Samba enables all active interfaces except the loopback interface (whose IP address 127.0.0.1)
One solution is to specify the name of only one active interface.
This can be set up as follows :

/etc/samba/smb.conf

interfaces = eth0