Importing f5-wsstar-ilx-0.4.3.tgz in TMOS 14.1.2.3 "General Database Error"

[F5Rob]

Importing f5-wsstar-ilx-0.4.3.tgz in TMOS 14.1.2.3 "General Database Error" Any idea why?

[Mikej81]

I have seen that error before, but cant remember the cause. Its probably related to the versions. Which file are you using for import? Should be this one: https://github.com/Mikej81/f5-wsstar-ilx/releases/download/0.4.3/f5_fakeadfs_ilx.tgz

[F5Rob]

This is the version I tried: https://github.com/Mikej81/f5-wsstar-ilx/releases/download/0.4.3/f5_fakeadfs_ilx.tgz looks the same. I am just going to create the workspace manually.

[Mikej81]

Roger. Let me know how it goes.

[F5Rob]

I manually imported all the code, ran npm update from /var/ilx/workspaces/Common/fakeadfs/extensions/f5_fakeadfs_ilx_extension and now get an error in the TMUI General database error retrieving information.General error: 01070711:3: boost::filesystem::status: Permission denied: "/var/ilx/workspaces/Common/fakeadfs/extensions/f5_fakeadfs_ilx_extension/node_modules/.bin/json5" in statement [SELECT COUNT(*) FROM dev_workspace WHERE name LIKE '%'] . The only way to see the workspaces now is to run rm -R fakeadfs from /var/ilx/workspaces/Common/

[Mikej81]

Thats odd. I dont have a 14.1.2.3 box online, I can try and get one spooled up today... What node version is on 14.1.2.3?

[F5Rob]

node v6.9.1

[F5Rob]

I found a support case that explains the problem and solution. Problem: TMUI General database error retrieving information.General error: 01070711:3: boost::filesystem::status: Permission denied: "/var/ilx/workspaces/Common/fakeadfs/extensions/f5_fakeadfs_ilx_extension/node_modules/.bin/json5" in statement [SELECT COUNT(*) FROM dev_workspace WHERE name LIKE '%'] Analysis: BIG-IP does not allow you to create symbolic links under workspaces irrespective of versions. It looks like permitted on the versions 14.0 and earlier, but they simply do not enforce the restriction strictly for activities outside of the control of tmsh (e.g., npm install or Unix commands). From 14.1, the new Unix (CentOS) is introduced, and the restriction is enforced stricter. Product Development team considers the symptom is by-design. Solution: npm --no-bin-links update

[Mikej81]

Ah. Cool. A workspace export from 14.1.2.3 should also work, maybe...