Re: Fwd: TFTP stopped working on F14
Hi Aron,
Johann proposed to check for /etc/xinetd.d/tftp - please try it.
What about xinetd? Is xinetd really running? You should find something
similar in /var/log/messages:
Oct 7 21:54:51 xinetd[12970]: xinetd Version 2.3.14 started
with libwrap loadavg labeled-networking options compiled in.
Oct 7 21:54:51 xinetd[12970]: Started working: 1 available
service
Oct 7 21:55:31 xinetd[12970]: START: tftp pid=12997
from=10.1.1.114
You mentioned usage of tcpdump (further in the thread). Did you check
the output?
Which version do you have currently installed? ('rpm -q' for tftp and
tftp-server)
Jiri
On Fri, 2011-10-07 at 16:38 +0100, Aaron Gray wrote:
> Hi,
>
>
> I think this is a development problem. I have tried everything obvious
> to get TFTP to work on F14 but to no avail. Could some one in the know
> look in to this please.
>
>
> I have tftp -server working on F14 and have done PXE Instillations
> using it. Since then I have done a yum update and ever since then have
> not been able to get it to work.
>
>
> Below in the two posts are what I have tried, as far as I can see it
> is exhaustive.
>
>
> Many thanks in advance,
>
>
> Aaron
>
> -- Forwarded message --
> From: Aaron Gray
> Date: 7 October 2011 15:48
> Subject: Re: TFTP stopped working on F14
> To: Thomas Dineen
> Cc: Community support for Fedora users
>
>
>
>
> On 7 October 2011 15:26, Thomas Dineen wrote:
> Aaron:
>
> 1) Update to the newest version of server and client.
> I have found that there are F14 and F15 bugs that are
> covered in the updates!
>
>
>
> I have done :-
>
>
> yum reinstall tftp
> yum reinstal tftp-server
>
>
> 2) Be aware of configuration requirements.
>
>
>
> It used to work, I installed two servers with PXE using it.
>
>
> 3) Be aware of SELinux, you will likely also have to enable
> variables in SELinux. Update you SELinux, more bugs here.
>
>
>
> I tried disable SELinux.
>
>
>
> 4) Of course recheck you firewall.
>
>
>
> -A INPUT -m state --state NEW -m udp -p udp --dport 69 -j ACCEPT
>
>
> But the firewall does not apply to local usage.
>
>
> Thomas Dineen
>
>
>
>
>
> Still not working :(
>
>
> Thanks,
>
>
> Aaron
>
>
>
> On 10/7/2011 7:07 AM, Aaron Gray wrote:
> > TFTP seems to have stopped working on my F14 machine.
> >
> >
> > It appears both server and client are not working.
> >
> >
> > I have it working on my F15 machine and have tried between
> > the two (with iptables rule) and F14 server and client do
> > not work.
> >
> >
> > tftp appears to log in but, on transferring a file it just
> > says "Transfer timed out." after a while.
> >
> >
> > I have reinstalled both client and server. And I am using
> > the same '/etc/xinetd.d/tftp' file on F15 as on F14.
> >
> >
> > There do not appear to be any logs for TFTP.
> >
> >
> > AFAICS I am not doing anything wrong or differently.
> >
> >
> > Help !
> >
> >
> > Many thanks in advance,
> >
> >
> > Aaron
> >
> >
> >
> >
>
>
>
>
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [ACTION REQUIRED v2] Retiring packages in F-16
On Tue, 2011-07-12 at 17:10 -0400, Bill Nottingham wrote: > Orphan netsniff-ng > comaintained by: fab No more orphaned. I've grabbed it Fedora+EPEL. Skalnik -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
GHC on ppc64 - current status & near future
Dear fans of Haskell and PowerPC, as was announced earlier Fedora for PowerPC has revived as a secondary arch. There are available images and repositories for Fedora 15 (ppc, ppc64) and the PowerPC release is planned for Fedora 16. GHC was available for ppc already in Fedora 12. Good news is bootstrapping ghc-7.0.2 for ppc64 in Fedora 15. You can find also a number of packages of Haskell platform that are built for ppc64 (20-25%). Builds for F16 are not available yet because of waiting for release of ghc-7.0.4 (RC1 was announced on Jun 03 by upstream). Fedora 16 should contain ppc64 builds of almost whole Haskell platform. These things will be announced here. Why 'almost'? Unfortunately ppc64 is listed among "Tier 2 platforms" by upstream - see http://hackage.haskell.org/trac/ghc/wiki/Platforms Especially ppc64 doesn't support GHCi (interactive environment) and NCG (Native Code Generator) yet. Due to this we wouldn't be able to build minimal following packages: - ghc-template-haskel - ghc-ForSyDe - ghc-QuickCheck - ghc-hamlet - ghc-parameterized-data - ghc-type-level I hope the list is probably completed and will not grow up. Ghceers Jiri -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: glibc-2.13.90-12 needs testing - re-adds RPC API
On Mon, 2011-05-16 at 14:26 -0400, Bill Nottingham wrote: > Notably, this re-adds the RPC API to glibc's exported interface, so > please test that rebuilding your applications still works, or works > again. > > https://admin.fedoraproject.org/updates/glibc-2.13.90-12 > there is number of headers that are no longer in glibc-headers (see comments in the link above). This is not surprise some builds fail. Is it somewhere documented? What about replacement? Is someone preparing -devel package containing missing headers? Thanks, Jiri -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: old_testing_critpath notifications
On Mon, 2010-11-29 at 14:34 +, Petr Pisar wrote: > On 2010-11-29, Peter Robinson wrote: > > On Mon, Nov 29, 2010 at 1:36 PM, Petr Pisar wrote: > >> On 2010-11-29, Peter Robinson wrote: > >>> On Mon, Nov 29, 2010 at 9:56 AM, Petr Pisar wrote: > >>> > > have no problems with it and I maintain around 120 packages. Filter it > > if you don't like it. > > Are you interrested in such notifications? Discussion about filtering/blocking mentioned messages is about how to fix consequence but... The discussion should search for improving source of the problem. What about source of this? I could count e.g.: - missing reaction of QA - missing approval for the package to be moved to stable - missing additional action of developer I've got a lot messages due to one package (needs modem for testing). I contacted some concerned people directly and I'm glad to say this situation has no more repeated with this package. This works fine. I believe only a little portion of packages are related to this problem. Well, I'm convinced better is "ask for action" then to discuss what "should/shouldn't happen". Skalnik -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
