devnull

Man of many talents. Server janitor, Chief Googler, Vice President of Pencil Sharpening, Director of Turning Things Off and On Again. Technology Plumber using Linux for stuff like Satellite STB, home CCTV system, kitchen sound bar, workstations, even car onboard computer. And servers, oh yeah - lots of them. I've been a Linux Mercenary for quite a while now, often using information posted by kind strangers on the Internet to solve problems during this journey. This blog is a humble attempt to give something back to the community.

thinlinc no password configured for vnc auth

 debian, thinlinc  No Responses »
Sep 082016
 

malamute

Got hit by this problem after upgrading Thinlinc 4.4 to 4.6 on one of my Debian Jessie boxes.

After upgrade process and setup completed I ran commands to get around Debian issues as documented here:

sudo update-rc.d vsmagent defaults
sudo update-rc.d vsmserver defaults
sudo update-rc.d tlwebaccess defaults
sudo update-rc.d tlwebadm defaults
read thinlinc version < /opt/thinlinc/etc/thinlinc-release
/opt/thinlinc/bin/tl-config /vsm/setup_completed=${version}
sudo service vsmagent start
sudo service vsmserver start
sudo service tlwebaccess start
sudo service tlwebadm start

Then  I tried reconnecting to the session and Thinlinc client generated dreaded “No password configured for vnc auth”. Error is not particularly clear  and the only clue from Thinlinc mailing list was

 

Typically, this error message indicates "disk full" on the server and 
similar problems. The user could also be out of quota. It could also be an 
issue with SELinux. Basically, if Xvnc cannot access 
/var/opt/thinlinc/sessions/${USER}/X/sessionkey, you will get this 
error.

which wasn’t the case here.

What helped, I murdered all “tl-session” processes and restarted vsm*

pkill tl-session
systemctl restart vsmagent vsmserver

and after that Thinlinc was more keen to start a session for me. Jolly good.

Generate ADU report with hpacucli Debian Jessie

 debian, linux, server  3 Responses »
Aug 192016
 

So you have faulty disk and these nice guys from HP (sorry, HPE I should say!) asked for adureport. That’s alright, it’s as easy as 1, 2, 3

Repository

Configure repository as described here.

Installation

apt-get install hpacucli

Generate report

hpacucli ctrl all diag file=/tmp/ADUReport.zip

Email report back to HP. You can of course view it first should you want it:

unzip ADUreport.zip 
vim ADUReport.txt

 

Using hpacucli

NB. Did you know, you can do all sorts of funky stuff with hpacucli?

Either run commands to get output that can be feed to monitoring scripts:

/usr/sbin/hpacucli ctrl slot=0 physicaldrive all show status
/usr/sbin/hpacucli ctrl slot=0 logicaldrive all show status
/usr/sbin/hpacucli ctrl slot=0 array all show status

or run it interactively:

/usr/sbin/hpacucli

HP Array Configuration Utility CLI 9.40.12.0
Detecting Controllers...Done.
Type "help" for a list of supported commands.
Type "exit" to close the console.

=>  ctrl all show config

<ommited>
=>  ctrl all show status

Smart Array P400 in Slot 0
   Controller Status: OK
   Cache Status: OK

=>   set target ctrl slot=0

 "controller slot=0"

=>   show

=>   show config detail

Smart Array P400 in Slot 0
   Bus Interface: PCI
   Slot: 2
   Serial Number: xxxxxxxxxxxxxxxx
   Cache Serial Number: xxxxxxxxxxx
   RAID 6 (ADG) Status: Disableds
   Controller Status: OK
   Chassis Slot:
   Hardware Revision: Rev E
   Firmware Version: 5.20
   Rebuild Priority: Medium
   Expand Priority: Medium
   Surface Scan Delay: 15 sec
   Cache Board Present: True
   Cache Status: OK
   Accelerator Ratio: 100% Read / 0% Write
   Drive Write Cache: Disabled
   Total Cache Size: 256 MB
   Battery Pack Count: 0
   SATA NCQ Supported: True

=> physicaldrive all show status

   physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 450 GB): OK
   physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 450 GB): OK
   physicaldrive 1I:1:3 (port 1I:box 1:bay 3, 450 GB): OK
   physicaldrive 1I:1:4 (port 1I:box 1:bay 4, 450 GB): OK
   physicaldrive 1I:1:5 (port 1I:box 1:bay 5, 450 GB): OK
   physicaldrive 1I:1:6 (port 1I:box 1:bay 6, 450 GB): OK
   physicaldrive 1I:1:7 (port 1I:box 1:bay 7, 450 GB): OK
   physicaldrive 1I:1:8 (port 1I:box 1:bay 8, 450 GB): OK
   physicaldrive 1I:1:9 (port 1I:box 1:bay 9, 450 GB): OK
   physicaldrive 1I:1:10 (port 1I:box 1:bay 10, 450 GB): OK
   physicaldrive 1I:1:11 (port 1I:box 1:bay 11, 450 GB, spare): OK
   physicaldrive 1I:1:12 (port 1I:box 1:bay 12, 450 GB, active spare): OK


=> array all show status

array AOK

=> logicaldrive all show status
   logicaldrive 1 (3.7 TB, 5): OK

If you don’t have battery or it takes long to replace it then you should enable no-battery write cache.

ctrl all show detail
hpacucli ctrl slot=0 modify nbwc=enable
hpacucli ctrl slot=0 modify dwc=enable forced
 Older Entries  Newer Entries