search

MeCJay12 / lsi-storage-authority

Dockerizing LSI Storage Authority, the replacement for MegaRaid Storage Manager, to manage MegaRAID cards.
1 stars 1 forks source link

[New Upstream Release] #2

Closed OdinVex closed 1 week ago

OdinVex commented 1 month ago

I believe there may be a new version, https://docs.broadcom.com/docs-and-downloads/raid-controllers/raid-controllers-common-files/007.020.016.000_LSA_Linux_x64.zip

MeCJay12 commented 4 weeks ago

Done. Took some extra time because I found a bug in my entrypoint along the way. New version is on tag :ubuntu_007.020.016.000 or :dev. I'll move it to :latest next week.

OdinVex commented 4 weeks ago

I recall that they added some anti-leech behavior to the URL (not sure if it exists for previous version?).

OdinVex commented 3 weeks ago

It also looks like e-mail capability is still failing for users. Broadcom is aware, they don't seem to have fixed it yet. I'm thinking about running a small docker that has an 'open' relay within the docker 'intranet' and simply forwards with a better smtp client to circumvent the issue.

MeCJay12 commented 3 weeks ago

Oh, yeah I use mwader/postfix-relay and it works well.

OdinVex commented 2 days ago

I swapped to the latest tag but the server never starts. I hijacked the entrypoint to provide a shell and ran /etc/init.d/LsiSASH start, status shows as not running still. I'm also not sure what the changes in entrypoint.sh were for. I don't think either of those segments involving file-copying and such should even exist really?

Edit: Yes, I did correct the appended /conf suffix to my path so it has the same pathing. Edit: The return from LsiSASH start is err 5. There is also no output (no "Starting LSI Storage Authority") or anything from LsiSASH either, no output of any kind.

Edit: For some reason I'm only getting an older image every time I pull for a new, 007.018.004.000 is what I'm getting using latest. :confused:

Edit: Found the issue. You've misspelled latest. You've got it as lastest.

MeCJay12 commented 2 days ago

Oof awkward. Typo corrected and bug resolved. Try it again. When a new container was made, the config file wasn't being created causing the service to boot loop.

For the upgrade still showing the old version of LSA, that sounds like you're mounting the whole /opt/lsi/LSIStorageAuthority/ directory instead of just /opt/lsi/LSIStorageAuthority/conf/. The service will not update files so if you mount the old binary it will boot the old binary.

OdinVex commented 2 days ago

Oof awkward. Typo corrected and bug resolved. Try it again. When a new container was made, the config file wasn't being created causing the service to boot loop.

For the upgrade still showing the old version of LSA, that sounds like you're mounting the whole /opt/lsi/LSIStorageAuthority/ directory instead of just /opt/lsi/LSIStorageAuthority/conf/. The service will not update files so if you mount the old binary it will boot the old binary.

Remember that I mentioned I was using /conf. The issue was only the typo.