I have just rebooted my server and I can now save changes, however, this is not really an acceptable approach! I also noticed that java.exe was using 800+ Mb of RAM, after reboot, around 100Mb!!
which did you reboot - the appserver or the server w/ the rcp gui? And which java was eating up 800+ of memory, the appserver or the gui?
The appserver has the RCP client on it, so both of them
It would be good to know which one it was. It could have been a problem w/ the gui only, or the appserver only.
I only have one server, it runs the appserver and has the GUI on, I rebooted it, and everything worked fine
I've seen this problem and thought I was going mad!
I was changing the option to pause at each stage during a Windows deployment in a job.
Everytime I told it to continue, clicked saved and ran a deployment. It would keep pausing!
I went round and round trying to find out why it wasn't saving.
I now exit the job after saving it, open it again, click save again, close the job again and keep doing that until the setting sticks.
Not a great solution
we have the same issue with BL server 8.0 with sp2 does not save changes to CERTAIN blpackages while saving them for most.
We're trying to change a property Action to something (e.g Add to Modify) for simple file deploy packages
I've checked all permissions (both Bladelogic and NTFS) for the "good" package that saves the change and the "bad" one and do not see any differences.
Nothing errors recorded in Audit Log, no errors in Application or Console Logs and I'm of course using the same id (BLAdmin) to make both changes
Visually I can tell that something is wrong when I try to save changes to the "bad" package Saving Dialog stays up a long time (no erros) then closes, then I close the package and it asks me again "Do you want to save changes"
When I save the "good" package the dialog flashes quickly and closes and I don't get the second Save prompt
So something goes wrong saving the "bad" package but no errors are recorded
We haven't rebooted the server as some other posts suggested this would be a horrible solution for us
I aslo have a case oped with BMC support on this but so far the only suggested was upgrading Application server to SP4 which is also not a good solution for us. they've mentioned something about bugs in the package editor maybe fixed in SP4 but no mentioning of wich bugs and besides editor is probably part of the gui (rcp) so I don't see the point
We've also tried updating the gui (on another server) to sp3 version and then connect to the SP2 server - same problem
Any ideas would be appreciated.
Can you update to sp3 or sp4, I think I remember hearing about the saving a blpackage issue. Check the release notes of the sp though. open a ticket w/ support to get the sp. You need to update the gui and appserver in lock step, so updating the gui to sp4 and not the appserver may not resolve the issue.
What is the issue updating to sp4? Your agents can stay at sp2 if you want.
in our environment app server
upgrade is a big deal
We have to be absolutely sure that the change will fix this issue I'll check the notes though, thanks
I've also asked support to come up with a temporary workaround for us meanwhile - waiting...
what is driving me mad is that I can't find anything different in the packages that fail to save vs those that save without any issues (most of them do)
why just these packages? There must be explanation
I even thought maybe it had something to do with the way we have Agent on the App Server configured when we push the ACLs to the app server and you said in our previous discussion that we should remove the agent from the App Serverhttp://communities.bmc.com/communities/message/154489#154489
Thread: "JNI file exists ... No authorization to access host"
maybe it fails to write to storage?
but all other packages update fine and file permissions on storage are the same
Do you have staging environment to reproduce/test this in?
Yes, I do but I can't reproduce it there
I tried importing the problem package into that environment but I can't reproduce the issue
I already have console sp3 there but it was done too quickly before we got a chance to first find any package that has the same problem now when we try to reproduce it we can never be sure if it works because of sp3 console upgrade or just because we never had this problem there
I've looked at sp4 notes but don't see anything that
related to our issue here
I think the problem comes down to the server failing to apply the change/ save bldeploy.xml file in package folder maybe its corrupted, maybe too big In the working package its size is 3k, the non-working package - 300K and the date is old. If I open the xml file on non-working package and manually make the change (in Notepad) save the file and packages shows up fine with updated setting in the console
Oh, what are you using as the editor? I think the built-in editor is the only r/w, I don't think if you open it w/ notepad you can actually save.