- 
                Notifications
    You must be signed in to change notification settings 
- Fork 14
Open
Labels
Description
From @AHumanFromCA on September 26, 2018 14:20
Opened this issue a while ago, I am transferring it over here since I do not see that it has been resolved yet.
I am unable to uninstall the DB2 plugin through Brightside.
The first uninstall attempt reports back that there is a locked file:
$ bright plugins uninstall @brightside/db2
npm ERR! path C:\Users\XXXXXXXX\.brightside\plugins\installed\node_modules\@brightside\db2\node_modules\ibm_db\installer\clidriver\bin\amd64.VC11.CRT
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall rmdir
npm ERR! EBUSY: resource busy or locked, rmdir 'C:\Users\XXXXXXXX\.brightside\plugins\installed\node_modules\@brightside\db2\node_modules\ibm_db\installer\clidriver\bin\amd64.VC11.CRT'
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\XXXXXXXX\AppData\Roaming\npm-cache\_logs\2018-07-30T21_24_21_271Z-debug.log
Command Error:
Uninstall Failed
Error Details:
Command failed: npm uninstall "@brightside/db2" --prefix C:\Users\XXXXXXXX\.brightside\plugins\installed -g
Sometimes this will break npm cache and make DB2 uninstallable without a complete reinstall.
My theory is that the lock somehow is gathered by the bright process due to these observations.
- It is always consistent that the first uninstall attempt fails at the ibm driver
- Installing DB2 and manually executing the failed command npm uninstall "@brightside/db2" --prefix C:\Users\XXXXXXXX\.brightside\plugins\installed -gwill uninstall the plugin's node folders every time.
That 2nd observation is why I believe that it isn't because of antivirus software.
| App | Version | 
|---|---|
| Brightside | 1.0.1 | 
| npm | 6.0.0 | 
| Node | 10.6.0 | 
| DB2 | 1.0.0 | 
Copied from original issue: gizafoundation/zowe-cli-db2-plugin#4
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Low Priority