Bug 229239

Summary: mail/postfix-policyd-spf-python throws magic number error on FreeBSD-11.1 jail
Product: Ports & Packages Reporter: James B. Byrne <byrnejb>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed Unable to Reproduce    
Severity: Affects Only Me CC: yasu
Priority: --- Flags: linimon: maintainer-feedback? (yasu)
Version: Latest   
Hardware: amd64   
OS: Any   

Description James B. Byrne 2018-06-22 20:25:20 UTC 
Environment: Ezjail jailed instance running on a FreeBSd-11.1 host.

OS: 
FreeBSD 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue May  8 05:21:56 UTC 2018     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

Installed via pkg:

py36-postfix-policyd-spf-python-2.0.2 Pure Python Postfix policy
daemon for SPF checking

When run from the command line the follwoing is observed:

/usr/local/bin/policyd-spf
Traceback (most recent call last):
  File "/usr/local/bin/policyd-spf", line 39, in <module>
    import spf
ImportError: bad magic number in 'spf': b'\x03\xf3\r\n'

This occurs on one jail.  Another jail, running on the same host, having the same installed packages, and  and configured identically except for the network addresses, does not display this error.
Comment 1 Yasuhiro Kimura freebsd_committer freebsd_triage 2019-01-21 02:45:57 UTC 
(In reply to James B. Byrne from comment #0)

Hello James.

Sorry for no response for such a long time. Does the problem still happen on the jail in question? If so then please execute 'pkg check -as' and see if invalid checksum errors are detected. And if no errors are found then please reinstall postfix-policyd-spf-python package after executing 'pkg delete -R python36'. Please keep in mind that this command remove all packages that depend on python36. So if there are other packages that depend on python36 then you need reinstall them too.

Best Regards.
Comment 2 James B. Byrne 2019-01-21 14:19:18 UTC 
You can close this issue.  We resolved the matter by deleting the jail and re-creating it.  The replacement jail did not encounter the error.  There must have been something abnormal in the creation of the original jail which triggered the error.  We could not reproduce it anywhere else.
Comment 3 Yasuhiro Kimura freebsd_committer freebsd_triage 2019-01-21 14:56:28 UTC 
(In reply to James B. Byrne from comment #2)

Thank you for reply. I agree with you that this bug report should be closed now. But it seems I don't have permission to change status of it. So would you please close it with the reason of 'Unable to Reproduce'?