Heads up: 7.3 breaks Self Service

RobertHammen
Valued Contributor II

If you use Self Service and scope policies to either Static or Smart Computer Groups, the policies may not show up in Self Service 7.3 following an upgrade of the suite to 7.3. Policies scoped to All Managed Clients/All Managed Servers still show up. Working with JAMF Support on this and apparently I'm not alone. May want to hold off on updating if this is important to you.

--Robert

14 REPLIES 14

bentoms
Release Candidate Programs Tester

Thanks for the warning!

Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883

dkucmierz
Contributor

Having the same issue, but I'm only scoping to AD user groups. I've been working with support on it as well, so hopefully a fix comes soon.

--

David Kucmierz
Mesquite ISD Technical Services
972.882.5506
dkucmierz at mesquiteisd.org

rdagel
New Contributor II

Same issue here thought i was going crazy!

rich

RobertHammen
Valued Contributor II
On Jul 16, 2010, at 3:10 PM, Dagel, Rich wrote: Same issue here thought i was going crazy! rich

Scoping to Static Groups, Smart Groups, or AD Groups?

After flushing the Tomcat cache via JSSUtil, mine's been working for 2 1/2 hrs. Policies show up, execute, the whole thing. Try it. Stop/restart Tomcat if it's still not working.

Some folks are having it where it'll run OK for awhile then stop. I'm waiting to see if I run into that issue.

Hope we/JAMF can get to the bottom of this.

--Robert

-----Original Message----- From: casper-bounces at list.jamfsoftware.com on behalf of David Kucmierz Sent: Fri 7/16/2010 10:54 AM To: Robert Hammen; List Casper Subject: Re: [Casper] Heads up: 7.3 breaks Self Service Having the same issue, but I'm only scoping to AD user groups. I've been working with support on it as well, so hopefully a fix comes soon. -- -----Original Message----- From: casper-bounces at list.jamfsoftware.com [mailto:casper-bounces at list.jamfsoftware.com] On Behalf Of Robert Hammen Sent: Friday, July 16, 2010 12:03 PM To: List Casper Subject: [Casper] Heads up: 7.3 breaks Self Service If you use Self Service and scope policies to either Static or Smart Computer Groups, the policies may not show up in Self Service 7.3 following an upgrade of the suite to 7.3. Policies scoped to All Managed Clients/All Managed Servers still show up. Working with JAMF Support on this and apparently I'm not alone. May want to hold off on updating if this is important to you. --Robert

Not applicable

Curious ­ is it just Self-Service, or are other policies affected? I just
had an issue where new policies were not being seen by several of my client
computers, while older ones were still running. A reboot of the server fixed
the hang-up, but of course the actual cause is still unknown. (This is under
7.21, btw, not 7.3)

Christopher Kemp
CNN Central Engineering

dkucmierz
Contributor

My only scoping is being done via AD groups, all the self service stuff is assigned to all computers, and is only affecting Self Service policies.

It works fine for me for an hour or 2, then the only things that are showing up in self service are policies not scoped by AD group.

Someone mentioned their every15 trigger, ours is set to every hour... maybe something in the periodic trigger is tripping up self service.

everything works fine for a while after restarting tomcat.

--

David Kucmierz
Mesquite ISD Technical Services
972.882.5506

RobertHammen
Valued Contributor II
On Jul 18, 2010, at 6:20 AM, Kemp, Chris wrote: Curious – is it just Self-Service, or are other policies affected?

Well, policies that are/should be scoped to you, do not show up in Self Service.

Somtimes stopping Tomcat and/or clearing caches will make it behave for some period of time (dependent upon your server and load, my guess), but eventually it'll fail again.

I just had an issue where new policies were not being seen by several of my client computers, while older ones were still running. A reboot of the server fixed the hang-up, but of course the actual cause is still unknown. (This is under 7.21, btw, not 7.3)

Probably not at all related to this issue (how much RAM/what are your settings?). 7.21 was pretty stable in my experience...

Not applicable

So if you create a normal policy right now, it runs fine? It's the odd
On 7/19/10 11:35 AM, "Robert Hammen" <rhlist1 at hammen.org> wrote:
policy behavior that caused me to ask about similarities between our issues.

I'm certain it's not the amount of RAM or Tomcat settings ­ they've been
functioning unchanged for months (the server itself has been rebooted once
or twice before this) and our installation is less that 100 computers so
it's not really taxing the Xserves heavily. Jamf support had no idea why
this was happening at the time. If it happens again, I'll try working with
Tomcat first to see if that helps.

The actual processes all appeared to be working ­ every15 was connecting &
running long-established policies, even older one-offs would run if I
flushed their history. However, these new policies simply wouldn't show up
to the clients. Running jamf manually from the command line I could see it
pick up the old flushed policies and re-execute them, but when it came to
the new ones it just checked in & said there was nothing to run, even after
re-creating the policy.

Christopher Kemp
CNN Central Engineering

jarednichols
Honored Contributor

Is this effecting policy scopes to individual computers, static or smart groups?

Thanks

j

Not applicable

The problem started with part of a static group (about 10 out of maybe 30
executed the policy); I also tested by assigning it to an individual
machine, one of the failed ones in the group. We don't have any smart groups
set up.

Christopher Kemp
CNN Central Engineering

![external image link](attachments/11824ea1d1c34ab1a8cc619cd5f291f6)

RobertHammen
Valued Contributor II

Both static and smart groups, in my experience.
On Jul 19, 2010, at 11:58 AM, Nichols, Jared - 1170 - MITLL wrote:

jarednichols
Honored Contributor

Lovely... Waiting for 7.31 then, I guess :)

rdagel
New Contributor II

Mine started working again. I rebooted the server and it worked find after
that. Even though I did a reboot after the upgrade. Very strange. Oh well
glad it is working now.

Rich

Rich Dagel
Senior Technology Specialist

Landor Associates
1001 Front Street
San Francisco, CA 94111
United States
415 365 3933
http://www.landor.com
Rich.Dagel at landor.com

RobertHammen
Valued Contributor II

I thought I was in the clear following clearing caches and a restart, except, like David, a few hours later a number of policies scoped to smart and/or static groups were missing until I restarted the Tomcat again...