# Wiretap gateway will not start **URL:** \ **Category:** Flame Questions\ **Tags:** wiretap\ **Created:** [July 11, 2022, 10:24am UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245 "2022-07-11T10:24:19Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 11, 2022, 10:24am UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/1 "2022-07-11T10:24:19Z")
I’ve just restarted Flame and now get an error message: Wiretap gateway service is unavailable Continue anyway? Choosing to continue will result in limited playback, import and export functionalities. I get a red light on the service monitor for wiretap gateway, which will not start. I’ve rebooted twice, and no joy. Ive tried this from the AD website: **Manage the Wiretap Gateway service from a Terminal with this command:** /etc/init.d/wiretapgateway \ But just get no such file or directory. I’m awaiting a call back from support, but thought I’d check to see if anyone here has an answer. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 12, 2022, 7:51am UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/3 "2022-07-12T07:51:03Z")
Running 2022.3.1 on centos 7.6 ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 12, 2022, 8:48am UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/5 "2022-07-12T08:48:42Z")
The service monitor loads but shows a red light light against the gateway, which refuses to start. Support were working on it yesterday for several hours and could not get it going. They’re going to try reinstalling the app and also upgrading the DKU. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 12, 2022, 10:15am UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/6 "2022-07-12T10:15:13Z")
Still no joy with it. They think that 2023 has done some damage. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 13, 2022, 9:21am UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/7 "2022-07-13T09:21:48Z")
So after 1 1/2 days of noodling, installing the latest DKU, uninstalling all versions of Flame, reinstalling 2002.3.1, the gateway will still not start. They have now run out of ideas! ---
**Author:** ![YannLaforest](https://avatars.discourse-cdn.com/v4/letter/y/c6cbf5/32.png) [@YannLaforest](https://forum.logik.tv/u/YannLaforest)\ **Post date:** [July 13, 2022, 12:08pm UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/8 "2022-07-13T12:08:34Z")
Hi @paul_round, Does “They” refer to the Autodesk technical support team? Best, Yann ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 13, 2022, 12:28pm UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/9 "2022-07-13T12:28:59Z")
No, Escape. I’ve yet to submit a ticket to AD. ---
**Author:** ![Jerem](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/jerem/32/6903_2.png) [@Jerem](https://forum.logik.tv/u/Jerem)\ **Post date:** [July 13, 2022, 1:57pm UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/10 "2022-07-13T13:57:12Z")
Hi Paul ! In our office I fixed this problem with a few things. Check in your security parameter you gave full access to disk for some protocol. like wiretap gateway, ifffswiretapserver, sw\_dbd , sw\_serverd… For us on all machine running 2022.3, we have to restart every day the stone + wire, if not flame start but impossible to cache any shots. It’s a bug of this version, I contact an engineer and he explain me that. Hope this will help you ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 13, 2022, 4:23pm UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/11 "2022-07-13T16:23:52Z")
This is on Linux, that sounds more like a mac. ---
**Author:** ![Fabi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fabi/32/14709_2.png) [@Fabi](https://forum.logik.tv/u/Fabi)\ **Post date:** [July 14, 2022, 3:32pm UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/12 "2022-07-14T15:32:24Z")
I had the same problem (MAC) the problem for me was that I had too many partitions I then deleted all superfluous partitions in the cfg file and replaced the cfg in the folder. The path to the cfg file is this: /opt/Autodesk/sw/stone+wire.cfg Maybe it helps… If you have found another solution, please write it here, I would be interested, Cheers…!! ---
**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\ **Post date:** [July 14, 2022, 4:03pm UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/13 "2022-07-14T16:03:50Z")
You’ll need to use the preformatted text button, which is the \ button in the Reply Window, to type paths. Like so. ```auto /opt/Autodesk/wrists ``` ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [July 14, 2022, 4:18pm UTC](https://forum.logik.tv/t/wiretap-gateway-will-not-start/6245/14 "2022-07-14T16:18:42Z")
This is not the issue here, as I said it’s Linux and Flame has been re-installed, so the issue must be deeper.