I just saw your post and was wondering if it was possible for you to use the latest version of mini_httpd (1.30) which is working well in https instead of the 1.27 you're actually using?
FYI, I tried to use mini_httpd 1.30 instead of napp-it-mhttpd, but it's not working properly. I can...
I've made tests on a second server, using 3 bakcplanes of 15 disks each, each backplane connected to a different SAS port on a Supermicro AOC S3216 HBA card. Napp-It version is 21.06.
When I issue the command echo "::mptsas -t" | sudo mdb -k to get disk info without sasircu, I got...
I've got a server with two SAS backplane which both are recognized as e0 m0 without sas3ircu, so I can map only half of the drives because the slot numbers are duplicated.
With sas3ircu, I properly got e0 m0 and e0 m1 (or is it e1 m0? I can't remember and I don't have access to the...
I'm currently using Napp-it on Omnios151038. When I use sas3ircu so I can get the correct slot info, I got the log file flooded by "FW Upload tce invalid!" warning messages.
I know these message aren't critical, but as it flood the messages log, it makes huge log files and its quite...
If anyone faces this driver problem, I solved-it using ESXi and the updated ixgben module from VMWare (VMware vSphere with Operations Management).
Maybe someday the driver will also be available on Solarish systems.
I've got a hand on a Supermicro A2SDi-H-TP4F (2 10G T and 2 SFP+), but no ports are recognized by Omnios.
As the Intel driver is the same as other Intel NIC (ixgbe), I wanted to know if anyone already get these working with OmniOS or any Solarish based OS.
I tested with the latest up to date...
I'm using latest OmniOS 151030
I well installed perl SSL and TLS module and enabled TLS email.
Here is the version installed:
cpan> notest install Net::SMTP::TLS
Net::SMTP::TLS is up to date (0.12).
cpan> notest install IO::Socket::SSL
IO::Socket::SSL is up to date (2.066).
@gea I can't use SMB for security and compatibility reasons. I'm going to try 151031 next week, and post my results
@DedoBOT Unfortunately Oplocks can't be deactivated at the client side for SMB > 1.
Another workaround for me is to use samba instead of native Solarish smb, as oplocks are shared...
After a full day of use, it seems that enabling oplocks was a bad idea as it induced a latency on many other programs.
So I'm quite stuck here. I don't know why Resolve needs oplocks enabled to work, while it's a problem for many others software...
As it's a server wide option, I can't activate...