Bug 426629 - asterisk fails to load the zaptel channel
Summary: asterisk fails to load the zaptel channel
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: asterisk
Version: 8
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeffrey C. Ollie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-23 09:39 UTC by Thomas Sailer
Modified: 2008-07-05 21:27 UTC (History)
2 users (show)

Fixed In Version: 1.4.21.1-1
Clone Of:
Environment:
Last Closed: 2008-07-05 21:27:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thomas Sailer 2007-12-23 09:39:37 UTC
Description of problem:
asterisk complains that it does not have permissions to open devices 
under /dev/zap/*, and thus fails to load the zaptel channel

Version-Release number of selected component (if applicable):
asterisk-1.4.16-1.fc8
asterisk-devel-1.4.16-1.fc8
asterisk-zaptel-1.4.16-1.fc8
zaptel-1.4.6-1.fc8
zaptel-devel-1.4.6-1.fc8
zaptel-lib-1.4.6-1.fc8
zaptel-utils-1.4.6-1.fc8

How reproducible:
always 

Steps to Reproduce:
1. service asterisk start
2. look under /var/log/asterisk/messages
  
Actual results:
[Dec 23 09:26:03] WARNING[17563] chan_zap.c: Unable to 
open '/dev/zap/channel': Permission denied
[Dec 23 09:26:03] ERROR[17563] chan_zap.c: Unable to open channel 1: 
Permission denied
here = 0, tmp->channel = 1, channel = 1
[Dec 23 09:26:03] ERROR[17563] chan_zap.c: Unable to register channel '1'


Expected results:
x*CLI> zap show channels
   Chan Extension  Context         Language   MOH Interpret
 pseudo            zapincoming     de         default
      1            sailerincoming  de         default
      4            zapincoming     de         default

Additional info:
asterisk starts as user root group root, but is instructed (via command line 
options) to setuid/setgid to user asterisk group asterisk. The zaptel devices 
are user zaptel group zaptel, with permissions rw-rw----. Now the intention 
was to add group zaptel as supplemental group to group asterisk. This cannot 
currently work however, since asterisk does, when switching users/groups, 
setgroups(0, NULL), thus dropping all supplemental groups.

Ways to fix:
1. patch asterisk to honour supplemental groups
2. add acl's to zaptel devices for group asterisk (or user asterisk)
3. have one group telephony instead of separate groups asterisk, zaptel

1 is probably the nicest.

Comment 1 Thomas Sailer 2007-12-23 09:55:12 UTC
Actually, asterisk does not need to be patched, it already does that if you 
_do not_ supply the -G argument. So I suggest you remove AST_GROUP from the 
initscript / sysconfig file

Comment 2 Tom Hughes 2008-02-01 14:12:22 UTC
I ran into this as well - zaptel was added (by something, not sure if it was
asterisk or zaptel) to the supplementary groups for asterisk, but that is then
ignored by asterisk.

Basically, asterisk has some weird logic where if you specify a user and a group
when starting it then it runs with exactly those permissions and discards all
supplementary groups. If you only specify a user then it takes that user's
default group and all that user's supplementary groups (including zaptel in this
instance).

My solution was the same as yours - removing the AST_GROUP setting from the
config file.

Comment 3 Fedora Update System 2008-02-19 13:59:21 UTC
asterisk-1.4.18-1.fc8 has been submitted as an update for Fedora 8

Comment 4 Fedora Update System 2008-02-19 15:55:44 UTC
asterisk-1.4.18-1.fc7 has been submitted as an update for Fedora 7

Comment 5 Fedora Update System 2008-02-21 02:53:26 UTC
asterisk-1.4.18-1.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update asterisk'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-1854

Comment 6 Robert Scheck 2008-07-05 18:39:52 UTC
The fix works for me, also added positive charma.


Note You need to log in before you can comment on or make changes to this bug.