Arch Linux User Repository

EDIT: The bug was located and fixed in a beta version after I reported it. The next official release of IPMIView will probably contain that fix.

I debugged the issue and the problem is that the aten supplied iKVM.jar does a reverse DNS lookup and checks for the existence of the hostname + .temp in the working directory, not the existence of the originally used IP address + temp.

IPMIView does not allow the usage of a DNS name in its settings. It does a DNS lookup and saves a IP address in the DNS answer as the address of the system. The UI of IPMIView also names the field "IP address", so using an IP address is expected of the user.

The only case in which iKVM.jar works correctly is if the attempt to retrieve the hostname fails. So you'd need to remove the PTR record for that IP address or create that temp file yourself and then call iKVM.jar from the commandline using the DNS name of the system or move the ip address + .temp named file and move it to the DNS name + .temp.

I have an issue open at supermicro regarding the "missing file" problem. If you report that, too, it might get more priority on their side. You don't need any support contract or something like that to do that.

Up to now the state is that they can't replicate the issue. I have been provided with the 2.14 release, which is the last version that works for me.

Link: https://uploadfiles.io/r0mxti4p

Still shows that "File missing, can not open KVM", even with "new version".

New version. Works if you change pkgver to 2.16.0 and _pkghash to 190528 and then updpkgsums.

A workaround for the "KVM missing file" problem:

cd /opt/ipmiview

java -Djava.library.path=. -jar iKVM.jar $IP $USERNAME $PASSWORD null 5900 623 2 0

replace $IP with your IP or DNS. $USERNAME and $PASSWORD is ADMIN/ADMIN per default config.

Found here: https://www.mcgill.org.za/stuff/archives/340

Is anyone else still having the "file missing" problem when trying to use the KVM? I've tried adding /opt/ipmiview to my $PATH but it still isn't working.

That wouldn't help. The application stores all settings in the directory it is in, so if another user then would try to run it, no settings could be loaded or saved. You basically need to make the application store the files somewhere in $HOME/.config/ipmiview or something, but we can't do it without patching the code, which includes decompiling, patching and recompiling. And that's evidently not an option due to the license. So I opted to just copy all files into the a user specific directory to ensure the the application's setting files are securely stored in $HOME and every user can actually use the application without problems.

:o

I could add a tmpfiles thing that sets permissions to something like 600 maybe?

@fryfrog All files that are not executable are configuration files.

IPMIView creates the configuration files as world read and writable, which includes those files containing your secrets. It creates those file in the directory that the script and java files are in. That is the reason I wrote the script in my last comment that copies all relevant executable files into ~/local/share/ipmiview. It makes sure that your secrets aren't world readable.

@fryfrog the following are the config files that should be placed in backup=:

• account.properties
• email.properties
• IPMIView.properties
• timeout.properties